Red Hat Bugzilla – Bug 835573
Last modified: 2014-03-30 21:29:00 EDT
Description of problem:
using localhost as a peer for mounting nfs and maintaining failover in a replciated volume
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create 2 brick replicated volume with 2 servers
2. add a third peer as a client
3. mount volume via nfs at localhost 'mount -t nfs -o vers=3 localhost:/volume /mnt/volume'
4. Fail brick 1 (reboot on server 1)
5. volume is inaccessible on client
6. bring brick back online and client can access volume
7. fail brick 2 (reboot server 2)
8. volume is still accessible by client
Volume becomes unavailable when the first brick fails
Volume should remain accessible in a replicated volume
Pretty sure this worked in 3.2
When server 1 is down for 42 seconds (standard timeout), the volume becomes accessible again. This does not seem to occur when server 2 goes down - the volume remains accessible.
it appears that" nfs_trusted_sync on" breaks failover of nfs volumes. with nfs_trusted_sync on, i get input/ouput error when 1 brick goes offline. when i reset this parameter, I am able to access the volume with one brick offline.
sorry for the confusion, this may not be a bug after all.
thanks firstname.lastname@example.org, closing the bug.