Bug 761946 (GLUSTER-214) - [ glusterfs 2.0.6rc4 ] - Unexpected behaviour upon replicate subvolume going read-only
Summary: [ glusterfs 2.0.6rc4 ] - Unexpected behaviour upon replicate subvolume going ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-214
Product: GlusterFS
Classification: Community
Component: replicate
Version: 2.0.5
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Vikas Gorur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-14 09:20 UTC by Gururaj K
Modified: 2010-01-25 07:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Gururaj K 2009-08-14 09:20:07 UTC
* 4 server distribute over replicate
* Client side WB, Server side IOT

* The second subvolume of replicate was remounted read-only after a hardware error. Some files were created before this happened. When these files were removed from the mountpoint, they still remained on the read-only subvolume.

* ls would not show one such file (a.out). However, a stat would successfully stat the file. However, self-heal was not triggered afer the stat


* After a while, stat on the file reported error:

[root@client03 fs-perf-test]# cd /mnt/pavan/rc4/client03/fs-perf-test
[root@client03 fs-perf-test]# ls a.out
ls: a.out: No such file or directory
[root@client03 fs-perf-test]# stat a.out
stat: cannot stat `a.out': No such file or directory
[root@client03 fs-perf-test]# echo 3 > /proc/sys/vm/drop_caches
[root@client03 fs-perf-test]# stat a.out
stat: cannot stat `a.out': No such file or directory


* The read-only subvolume remains unchanged:

support@dev:/share/guru$ kash -n brick[5-8] ls /jbod/pavan/exp26rc4/client03/fs-perf-test/a.out*
--------------------------------------------------------------------------------
STDOUT
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
brick8 (1 HOST)
--------------------------------------------------------------------------------
/jbod/pavan/exp26rc4/client03/fs-perf-test/a.out
--------------------------------------------------------------------------------
brick7 (1 HOST)
--------------------------------------------------------------------------------
/jbod/pavan/exp26rc4/client03/fs-perf-test/a.out1
--------------------------------------------------------------------------------
STDERR
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
brick[5-6] (2 HOSTS)
--------------------------------------------------------------------------------
ls: /jbod/pavan/exp26rc4/client03/fs-perf-test/a.out*: No such file or directory

Comment 1 Vikas Gorur 2010-01-25 04:20:53 UTC
Fixed in 3.0


Note You need to log in before you can comment on or make changes to this bug.