[Bugs] [Bug 1138970] file corruption during concurrent read/write

[bugzilla at redhat.com]

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



--- Comment #8 from Raghavendra G <rgowdapp at redhat.com> ---
Seems like there is no permanent corruption (though the reader running
concurrently with write gets wrong sequence number)

[root at booradley 1138970]# >/mnt/glusterfs/file;
./gluster-fuse-client-interleaved-read-write-corruption.py /mnt/glusterfs/file
[root at booradley 1138970]# cp -fv /mnt/glusterfs/file .
`/mnt/glusterfs/file' -> `./file'
[root at booradley 1138970]# >/mnt/glusterfs/file;
./gluster-fuse-client-interleaved-read-write-corruption.py /mnt/glusterfs/file
[root at booradley 1138970]# >/mnt/glusterfs/file;
./gluster-fuse-client-interleaved-read-write-corruption.py /mnt/glusterfs/file
FAILED: expected record id 58 retrieved record id 59
[root at booradley 1138970]# diff /mnt/glusterfs/file ./file 
[root at booradley 1138970]# >/mnt/glusterfs/file;
./gluster-fuse-client-interleaved-read-write-corruption.py /mnt/glusterfs/file
FAILED: expected record id 39 retrieved record id 40
[root at booradley 1138970]# diff /mnt/glusterfs/file ./file 

As can be seen above, I am comparing the file where:
1. the script reported an error
2. the script didn't report an error

diff didn't report any difference b/w both files above. This seems to point to
corruption being transient, where reader got corrupted data only when executing
with a concurrent writer.

-- 
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=bEtsQ5LKwd&a=cc_unsubscribe