Displaying 17 results from an estimated 17 matches for "dht_selfheal_directory".
2025 Jan 28
1
Glusterfs mounts on clients with few bricks missing
...ro,_netdev 0 0" where 10.132.2.101
is one of the nodes and datavol is the volume name.
Any help would be appreciated. In the client glusterfs log we see the below
prints in case these help to figure out the issue.
[2025-01-28 11:00:11.404092 +0000] W [MSGID: 109222]
> [dht-selfheal.c:2024:dht_selfheal_directory] 0-datavol-dht: Directory
> selfheal failed [{path=/}, {subvol-down=1}, {Not-fixing}, {gfid=}]
> [2025-01-28 11:00:11.405029 +0000] W [dict.c:1532:dict_get_with_ref]
> (-->/usr/lib64/glusterfs/9.3/xlator/cluster/distribute.so(+0x556ea)
> [0x7f63cdf176ea] -->/lib64/libglusterfs.so....
2018 Apr 05
2
[dht-selfheal.c:2328:dht_selfheal_directory] 0-data-dht: Directory selfheal failed: Unable to form layout for directory /
Hi,
I noticed when I run gluster volume heal data info, the follow message
shows up in the log, along with other stuff:
[dht-selfheal.c:2328:dht_selfheal_directory] 0-data-dht: Directory selfheal
> failed: Unable to form layout for directory /
I'm seeing it on Gluster 4.0.1 and 3.13.2.
Here's the full log after running heal info:
https://gist.github.com/fa19201d064490ce34a512a8f5cb82cc.
Any idea why this could be?
Thanks.
Sincerely,
Artem
--...
2018 Apr 05
0
[dht-selfheal.c:2328:dht_selfheal_directory] 0-data-dht: Directory selfheal failed: Unable to form layout for directory /
On Thu, Apr 5, 2018 at 10:48 AM, Artem Russakovskii <archon810 at gmail.com>
wrote:
> Hi,
>
> I noticed when I run gluster volume heal data info, the follow message
> shows up in the log, along with other stuff:
>
> [dht-selfheal.c:2328:dht_selfheal_directory] 0-data-dht: Directory
>> selfheal failed: Unable to form layout for directory /
>
>
> I'm seeing it on Gluster 4.0.1 and 3.13.2.
>
This msg is harmless. You can ignore it for now. There is a fix in works at
https://review.gluster.org/19727
> Here's the full log afte...
2025 Jan 28
1
Glusterfs mounts on clients with few bricks missing
...01 is one of the nodes and datavol is the?volume name.
>
> Any help would be appreciated. In the client glusterfs log we see
> the?below prints in case these help to figure out the?issue.?
>
> > [2025-01-28 11:00:11.404092 +0000] W [MSGID: 109222] [dht-
> > selfheal.c:2024:dht_selfheal_directory] 0-datavol-dht: Directory
> > selfheal failed [{path=/}, {subvol-down=1}, {Not-fixing}, {gfid=}]
> > [2025-01-28 11:00:11.405029 +0000] W
> > [dict.c:1532:dict_get_with_ref] (--
> > >/usr/lib64/glusterfs/9.3/xlator/cluster/distribute.so(+0x556ea)
> > [0x7f63cdf176ea...
2017 Nov 09
2
Error logged in fuse-mount log file
...rs at gluster.org<mailto:gluster-users at gluster.org>>
Hi,
I am using glusterfs 3.10.1 and i am seeing below msg in fuse-mount log file.
what does this error mean? should i worry about this and how do i resolve this?
[2017-11-07 11:59:17.218973] W [MSGID: 109005] [dht-selfheal.c:2113:dht_selfheal_directory] 0-glustervol-dht: Directory selfheal fail
ed : 1 subvolumes have unrecoverable errors. path = /fol1/fol2/fol3/fol4/fol5, gfid =3f856ab3-f538-43ee-b408-53dd3da617fb
[2017-11-07 11:59:17.218935] I [MSGID: 109063] [dht-layout.c:713:dht_layout_normalize] 0-glustervol-dht: Found anomalies in /fol1/fol2...
2017 Nov 13
2
Error logged in fuse-mount log file
...;
>> I am using glusterfs 3.10.1 and i am seeing below msg in fuse-mount log
>> file.
>>
>> what does this error mean? should i worry about this and how do i resolve
>> this?
>>
>> [2017-11-07 11:59:17.218973] W [MSGID: 109005]
>> [dht-selfheal.c:2113:dht_selfheal_directory] 0-glustervol-dht: Directory
>> selfheal fail
>> ed : 1 subvolumes have unrecoverable errors. path =
>> /fol1/fol2/fol3/fol4/fol5, gfid =3f856ab3-f538-43ee-b408-53dd3da617fb
>> [2017-11-07 11:59:17.218935] I [MSGID: 109063]
>> [dht-layout.c:713:dht_layout_normalize] 0-...
2017 Nov 10
0
Error logged in fuse-mount log file
...r.org>
>
>
> Hi,
>
> I am using glusterfs 3.10.1 and i am seeing below msg in fuse-mount log
> file.
>
> what does this error mean? should i worry about this and how do i resolve
> this?
>
> [2017-11-07 11:59:17.218973] W [MSGID: 109005]
> [dht-selfheal.c:2113:dht_selfheal_directory] 0-glustervol-dht: Directory
> selfheal fail
> ed : 1 subvolumes have unrecoverable errors. path =
> /fol1/fol2/fol3/fol4/fol5, gfid =3f856ab3-f538-43ee-b408-53dd3da617fb
> [2017-11-07 11:59:17.218935] I [MSGID: 109063]
> [dht-layout.c:713:dht_layout_normalize] 0-glustervol-dht: Foun...
2017 Nov 14
2
Error logged in fuse-mount log file
...le
To: Gluster Users < gluster-users at gluster.org >
Hi,
I am using glusterfs 3.10.1 and i am seeing below msg in fuse-mount log file.
what does this error mean? should i worry about this and how do i resolve this?
[2017-11-07 11:59:17.218973] W [MSGID: 109005] [dht-selfheal.c:2113:dht_selfheal_directory] 0-glustervol-dht: Directory selfheal fail
ed : 1 subvolumes have unrecoverable errors. path = /fol1/fol2/fol3/fol4/fol5, gfid =3f856ab3-f538-43ee-b408-53dd3da617fb
[2017-11-07 11:59:17.218935] I [MSGID: 109063] [dht-layout.c:713:dht_layout_normalize] 0-glustervol-dht: Found anomalies in /fol1/fo...
2017 Nov 13
0
Error logged in fuse-mount log file
...rfs 3.10.1 and i am seeing below msg in fuse-mount log
>>> file.
>>>
>>> what does this error mean? should i worry about this and how do i
>>> resolve this?
>>>
>>> [2017-11-07 11:59:17.218973] W [MSGID: 109005]
>>> [dht-selfheal.c:2113:dht_selfheal_directory] 0-glustervol-dht:
>>> Directory selfheal fail
>>> ed : 1 subvolumes have unrecoverable errors. path =
>>> /fol1/fol2/fol3/fol4/fol5, gfid =3f856ab3-f538-43ee-b408-53dd3da617fb
>>> [2017-11-07 11:59:17.218935] I [MSGID: 109063]
>>> [dht-layout.c:713:dht_...
2017 Nov 14
0
Error logged in fuse-mount log file
...and i am seeing below msg in fuse-mount log
>>>> file.
>>>>
>>>> what does this error mean? should i worry about this and how do i
>>>> resolve this?
>>>>
>>>> [2017-11-07 11:59:17.218973] W [MSGID: 109005] [dht-selfheal.c:2113:dht_selfheal_directory]
>>>> 0-glustervol-dht: Directory selfheal fail
>>>> ed : 1 subvolumes have unrecoverable errors. path =
>>>> /fol1/fol2/fol3/fol4/fol5, gfid =3f856ab3-f538-43ee-b408-53dd3da617fb
>>>> [2017-11-07 11:59:17.218935] I [MSGID: 109063]
>>>> [d...
2017 Nov 07
0
error logged in fuse-mount log file
Hi,
I am using glusterfs 3.10.1 and i am seeing below msg in fuse-mount log
file.
what does this error mean? should i worry about this and how do i resolve
this?
[2017-11-07 11:59:17.218973] W [MSGID: 109005]
[dht-selfheal.c:2113:dht_selfheal_directory] 0-glustervol-dht: Directory
selfheal fail
ed : 1 subvolumes have unrecoverable errors. path =
/fol1/fol2/fol3/fol4/fol5, gfid =3f856ab3-f538-43ee-b408-53dd3da617fb
[2017-11-07 11:59:17.218935] I [MSGID: 109063]
[dht-layout.c:713:dht_layout_normalize] 0-glustervol-dht: Found anomalies
in /fol1/fol2...
2013 Feb 26
0
Replicated Volume Crashed
...-02-25 19:56:20.623378] I [dht-layout.c:593:dht_layout_normalize]
0-adata-dht: found anomalies in /files. holes=1 overlaps=0
[2013-02-25 19:56:20.623399] W [dht-layout.c:186:dht_layout_search]
0-adata-dht: no subvolume for hash (value) = 2967408968
[2013-02-25 19:56:20.623404] W [dht-selfheal.c:882:dht_selfheal_directory]
0-adata-dht: 1 subvolumes have unrecoverable errors
[2013-02-25 19:56:20.623413] E [dht-common.c:1372:dht_lookup] 0-adata-dht:
Failed to get hashed subvol for /files/random-file.dat
[2013-02-25 19:57:02.780965] W [fuse-bridge.c:292:fuse_entry_cbk]
0-glusterfs-fuse: 3960898: LOOKUP() /files/random-...
2018 Apr 09
2
Gluster cluster on two networks
...11:35:31.405585] I [MSGID: 114035] [client-handshake.c:202:client_set_lk_version_cbk] 5-urd-gds-volume-client-5: Server lk version = 1
[2018-04-09 11:42:29.622006] I [fuse-bridge.c:4835:fuse_graph_sync] 0-fuse: switched to graph 5
[2018-04-09 11:42:29.627533] I [MSGID: 109005] [dht-selfheal.c:2458:dht_selfheal_directory] 5-urd-gds-volume-dht: Directory selfheal failed: Unable to form layout for directory /
[2018-04-09 11:42:29.627935] I [MSGID: 114021] [client.c:2369:notify] 2-urd-gds-volume-client-0: current graph is no longer active, destroying rpc_client
[2018-04-09 11:42:29.628013] I [MSGID: 114021] [client.c:...
2018 Apr 10
0
Gluster cluster on two networks
...[MSGID: 114035] [client-handshake.c:202:client_set_lk_version_cbk]
> 5-urd-gds-volume-client-5: Server lk version = 1
> [2018-04-09 11:42:29.622006] I [fuse-bridge.c:4835:fuse_graph_sync]
> 0-fuse: switched to graph 5
> [2018-04-09 11:42:29.627533] I [MSGID: 109005] [dht-selfheal.c:2458:dht_selfheal_directory]
> 5-urd-gds-volume-dht: Directory selfheal failed: Unable to form layout for
> directory /
> [2018-04-09 11:42:29.627935] I [MSGID: 114021] [client.c:2369:notify]
> 2-urd-gds-volume-client-0: current graph is no longer active, destroying
> rpc_client
> [2018-04-09 11:42:29.628013...
2018 Apr 10
1
Gluster cluster on two networks
...ent-handshake.c:202:client_set_lk_version_cbk]
> > 5-urd-gds-volume-client-5: Server lk version = 1
> > [2018-04-09 11:42:29.622006] I [fuse-bridge.c:4835:fuse_graph_sync]
> > 0-fuse: switched to graph 5
> > [2018-04-09 11:42:29.627533] I [MSGID: 109005] [dht-selfheal.c:2458:dht_selfheal_directory]
> > 5-urd-gds-volume-dht: Directory selfheal failed: Unable to form layout for
> > directory /
> > [2018-04-09 11:42:29.627935] I [MSGID: 114021] [client.c:2369:notify]
> > 2-urd-gds-volume-client-0: current graph is no longer active, destroying
> > rpc_client
> &g...
2018 Apr 10
0
Gluster cluster on two networks
...11:35:31.405585] I [MSGID: 114035] [client-handshake.c:202:client_set_lk_version_cbk] 5-urd-gds-volume-client-5: Server lk version = 1
[2018-04-09 11:42:29.622006] I [fuse-bridge.c:4835:fuse_graph_sync] 0-fuse: switched to graph 5
[2018-04-09 11:42:29.627533] I [MSGID: 109005] [dht-selfheal.c:2458:dht_selfheal_directory] 5-urd-gds-volume-dht: Directory selfheal failed: Unable to form layout for directory /
[2018-04-09 11:42:29.627935] I [MSGID: 114021] [client.c:2369:notify] 2-urd-gds-volume-client-0: current graph is no longer active, destroying rpc_client
[2018-04-09 11:42:29.628013] I [MSGID: 114021] [client.c:...
2012 Feb 22
2
"mismatching layouts" errors after expanding volume
Dear All-
There are a lot of the following type of errors in my client and NFS
logs following a recent volume expansion.
[2012-02-16 22:59:42.504907] I
[dht-layout.c:682:dht_layout_dir_mismatch] 0-atmos-dht: subvol:
atmos-replicate-0; inode layout - 0 - 0; disk layout - 9203501
34 - 1227133511
[2012-02-16 22:59:42.534399] I [dht-common.c:524:dht_revalidate_cbk]
0-atmos-dht: mismatching