[Bugs] [Bug 1387499] Should not display wrong information by stat when data heal is pending for a non-zero size file
bugzilla at redhat.com
bugzilla at redhat.com
Sun Nov 20 17:03:54 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1387499
Pranith Kumar K <pkarampu at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ravishankar at redhat.com
Flags| |needinfo?(ravishankar at redha
| |t.com)
--- Comment #5 from Pranith Kumar K <pkarampu at redhat.com> ---
On fuse mount stat is converted as Lookup. If Lookup on such files fail, unlink
on such files will never happen. Especially the files which are in split-brain.
While it does show file's stat output as wrong, nothing much can be done with
contents of such data:
root at dhcp35-190 - ~
22:26:41 :) ⚡ gluster v heal r2 info
Brick localhost.localdomain:/home/gfs/r2_0
Status: Connected
Number of entries: 0
Brick localhost.localdomain:/home/gfs/r2_1
Status: Transport endpoint is not connected
Number of entries: -
Brick localhost.localdomain:/home/gfs/r2_2
/di1/a
Status: Connected
Number of entries: 1
root at dhcp35-190 - ~
22:26:46 :) ⚡ ls -l /mnt/r2/di1
total 0
-rw-r--r--. 1 root root 0 Nov 20 22:24 a
root at dhcp35-190 - ~
22:26:53 :) ⚡ cp -r /mnt/r2/di1/ /mnt/r2/di2
cp: error reading '/mnt/r2/di1/a': Input/output error <<-----
root at dhcp35-190 - ~
22:30:41 :( ⚡ truncate -s 0 /mnt/r2/di1/a
truncate: failed to truncate '/mnt/r2/di1/a' at 0 bytes: Input/output error
root at dhcp35-190 - ~
22:30:48 :( ⚡ echo abc > /mnt/r2/di1/a
-bash: /mnt/r2/di1/a: Input/output error
root at dhcp35-190 - ~
22:30:56 :( ⚡ unlink /mnt/r2/di1/a <<---- Only deletion is successful.
Ravi,
I was under the impression that the 'cp -r' would succeed, it just
occurred to me that I wasn't thinking through it correctly. I think we can fix
this a bit later also.
Could you check the above cases work the same for other protocols like
NFS/Samba? If yes we can defer this.
Pranith
--
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=sdTq8cT1Of&a=cc_unsubscribe
More information about the Bugs
mailing list