Displaying 6 results from an estimated 6 matches for "43fd".
Did you mean:
43f4
2003 Dec 20
2
More beginner questions
...sip:91184@82.38.193.149>;tag=as1f0e4544
To: <sip:612@fwd.pulver.com>;tag=as63b4567c
Call-ID: 4336592d02a1a1ba7173c842778e8b8e@82.38.193.149
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Contact: <sip:612@65.39.205.112:5028>
Content-Length: 0
9 headers, 0 lines
-- SIP/fwd.pulver.com-43fd is ringing
Sip read: CLI>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 82.38.193.149:5060;branch=z9hG4bK42c80372
From: "calisto" <sip:91184@82.38.193.149>;tag=as1f0e4544
To: <sip:612@fwd.pulver.com>;tag=as2046b5cb
Call-ID: 4336592d02a1a1ba7173c842778e8b8e@82.38.193.149
CSeq: 102 IN...
2013 Aug 29
2
bug
...on five disks using RAID5 (-d raid5 for mount option). When a power failure occurs, I can not remount btrfs after my system reboots. Dmesg for remount is presented as following:
[ 192.713953] bio: create slab <bio-1> at 1
[ 192.716230] Btrfs loaded
[ 192.717177] device fsid a0dff7ea-9354-43fd-8516-0e17f370991d devid 1 transid 6 /dev/sdb
[ 192.717712] btrfs: disk space caching is enabled
[ 192.720572] btrfs: failed to read the system array on sdb
[ 192.723398] btrfs: open_ctree failed
linux md raid5 have resync , the test seems btrfs raid5 have not resync,how fix the bug?
--
To...
2005 Apr 22
4
I have a problem similar to FAQ 2 scenario, but reply packets don''t seem to be recognized.
...c3:9d:ac, ethertype IPv4
(0x0800), length 74: IP (tos 0x0, ttl 64, id 46520, offset 0, flags [DF],
length: 60) 192.168.0.150.35238 > 65.40.217.150.443: S [tcp sum ok]
353484362:353484362(0) win 5840 <mss 1460,sackOK,timestamp 3624012786
0,nop,wscale 2>
0x0000: 0000 f4c3 9dac 0011 43fd 4dca 0800 4500 ........C.M...E.
0x0010: 003c b5b8 4000 4006 a906 c0a8 0096 4128 .<..@.@.......A(
0x0020: d996 89a6 01bb 1511 be4a 0000 0000 a002 .........J......
0x0030: 16d0 1286 0000 0204 05b4 0402 080a d802 ................
0x0040: 0bf2 0000 0000 0103 0...
2017 Oct 26
0
not healing one file
Hey Richard,
Could you share the following informations please?
1. gluster volume info <volname>
2. getfattr output of that file from all the bricks
getfattr -d -e hex -m . <brickpath/filepath>
3. glustershd & glfsheal logs
Regards,
Karthik
On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote:
> On a side note, try recently released health
2017 Oct 26
3
not healing one file
On a side note, try recently released health report tool, and see if it
does diagnose any issues in setup. Currently you may have to run it in all
the three machines.
On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote:
> Thanks for this report. This week many of the developers are at Gluster
> Summit in Prague, will be checking this and respond next
2017 Oct 26
2
not healing one file
...327:afr_log_selfheal] 0-home-replicate-0: Completed metadata selfheal on f0e844b6-9358-43d1-a8bf-02d3ae55c485. sources=0 [2] sinks=1
[2017-10-25 10:40:11.018525] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on 9917cfd6-bbac-4608-b778-43fdcb5d802c. sources=0 [2] sinks=1
[2017-10-25 10:40:11.019840] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on 9917cfd6-bbac-4608-b778-43fdcb5d802c
[2017-10-25 10:40:11.023123] I [MSGID: 108026] [afr-self-heal-common.c:13...