[Bugs] [Bug 1303153] Gluster creating 0 byte files

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1303153

Nithya Balachandran <nbalacha at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



--- Comment #10 from Nithya Balachandran <nbalacha at redhat.com> ---
The 0 byte file is missing an xattr.
DHT uses these 0 byte "linkto" files as an internal mechanism to help it find
the brick on which the actual data file exists. It identifies these files using
the sticky bit and the trusted.glusterfs.dht.linkto xattr. If the xattr is
missing, DHT treats it as a data file and shows it on the mount. As the
non-zero byte file is also not a linkto file as per DHT, it will also be listed
so you will see 2 entries, however the properties will be those of the one read
first.

If you are certain that the non-zero byte file, henceforth referred to as the
data file, contains the right information, please delete the 0 byte file from
the backend bricks. Do _not_ try to delete it from the mountpoint - it could
end up deleting the data file. Once you have deleted the linkto file from both
bricks in the replica set, you should be able to see and access the correct
file from the mountpoint. 

Doing an ls on the file after that should recreate the linkto file with the
xattr set.

Are there any other files with this problem? Are there any error messages in
the glusterfs client logs to indicate any problems with this file?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=5pxJWW2yEi&a=cc_unsubscribe