On Wed, 20 Mar 2019 at 22:59, Jim Kinney <jim.kinney at gmail.com> wrote:
> I have half a zillion broken symlinks in the .glusterfs folder on 3 of 11
> volumes. It doesn't make sense to me that a GFID should linklike some
of
> the ones below:
>
>
/data/glusterfs/home/brick/brick/.glusterfs/9e/75/9e75a16f-fe4f-411e-937d-1a6c4758fd0e
> -> ../../c7/6f/c76ff719-dde6-41f5-a327-7e13fdf6ec4b/bundle2
>
/data/glusterfs/home/brick/brick/.glusterfs/9e/75/9e7594de-c68a-44d0-a959-46ceb628c28b
> -> SSL_CTX_set0_CA_list.html
>
/data/glusterfs/home/brick/brick/.glusterfs/9e/75/9e75a40b-990f-4dd5-8aaa-9996da0fbdf4
> -> ../../46/93/4693face-affb-4647-bcd0-919bccc82c42/labeled_tensor
>
/data/glusterfs/home/brick/brick/.glusterfs/9e/75/9e75eb33-2941-461f-aa50-394a8e9cbba1
> -> libtiff.so.5.2.6
>
> The links are pointing to file names in the .glusterfs directories.
> Shouldn't all of these be symlinks to other GFID entries and not
contain
> text like "bundle2" and "labeled_tensor"?
>
>
> Hi,
These bundle2 and labeled_tensor links are fine - they are gfids of
directories, not files, so the symlinks created will point to the parent
handle+dirname.
The ones pointing to SSL_CTX_set0_CA_list.html and libtiff.so.5.2.6 look
odd. They should not be symlinks . File handles should be hardlinks.
Regards,
Nithya
-- >
> James P. Kinney III Every time you stop a school, you will have to build a
> jail. What you gain at one end you lose at the other. It's like feeding
a
> dog on his own tail. It won't fatten the dog. - Speech 11/23/1900 Mark
> Twain http://heretothereideas.blogspot.com/
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20190321/35bf0ee1/attachment.html>