[Gluster-devel] heal info output

Emmanuel Dreyfus manu at netbsd.org
Thu Jul 2 01:05:27 UTC 2020


Hello

gluster volume heal info show me questionable entries. I wonder if these
are bugs, or if I shoud handle them and how.

bidon# gluster volume heal gfs info 
Brick bidon:/export/wd0e_tmp
Status: Connected
Number of entries: 0

Brick baril:/export/wd0e
/.attribute/system 
<gfid:7f3a4aa5-7a49-4f50-a166-b345cdf0616c> 
Status: Connected
Number of entries: 2

(...)
Brick bidon:/export/wd2e
<gfid:d616f804-0579-4649-8d8e-51ec4cf0e131> 
<gfid:f4eb6db3-8341-454b-9700-81ad4ebca61e> 
/owncloud/data 
<gfid:43b80fd9-a577-4568-b400-2d80bb4d25ad> 
<gfid:7253faad-6843-4321-a63f-17671237d607> 
<gfid:da055475-43c0-4157-b4f1-30b3647bc0b6> 
<gfid:02f4f38e-f351-4bb8-bd43-cad64ba5a4f5> 

There are three cases:
1) /.attribute directory is special on NetBSD, it is where extended
attributes are stored for the filesystem. The posix xlator takes care of
screening it, but there must be some other softrware component that
should learn it must disregeard it. Hints are welcome about where I
should look at.

2) /owncloud/data  is a directory. mode, owner and groups are the same
on bricks. Why is it listed here?

3) <gfid:...> What should I do with this?
-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu at netbsd.org


More information about the Gluster-devel mailing list