Juha Jäykkä wrote: >> As soon as the client comes across a RW volume the path will be a RW >> path. Therefore the clients will not switch. Are you sure your >> clients are really using RO versions of the volume? > > Yes, I understand this. This is why I wrote "Now users' $HOME is, of > course, the RW version (/afs/blablabla/.username) and programs using $HOME > will complain when A disappears." > > What we exactly did was this. We simulated a crashed host by unplugging > the ethernet cable of A (housing RW and RO of everything) so only B > (housing another RO copies) and C (with no volumes) were available. After > that, all RW paths became inaccessible, as they should. > > We came about implementing AFS for precisely the reason that losing users' > home dirs in case of a crashed file server is something we want to avoid. > Obviously we'll lose the ability to write to home dirs, but that is just > an inconveniency: users are able to get things done by reading the files > off the RO replica and temporarily writing their files to local discs.
But if the home directories are set to the RW paths, then there will be no failover to the RO volumes. The RW paths will only access the RW volumes. > Should this work? We tried accessing the RO replica with "ls -l > /afs/tfy.utu.fi/home/username", but got nothing back. This does, however, > work if we remove the replica from A and only have one RO replica at B. I > even tried fs flushmount and flushvolume before the ls. The questions you need to answer are: is the volume pointed to by /afs/tfy.utu.fi/ a RO volume and is it replicated? is the volume pointed to by /afs/tfy.utu.fi/home/ a RO volume and is it replicated? is the volume pointed to by /afs/tfy.utu.fi/home/username/ a RO volume and is it replicated? Normally you want a RO replica on the same machine as the RW volume in order to reduce the time the RW volume is inaccessible during the volume release process. Once the release is done locally the RO only copy can be sync'd with the rest of the replicas. If this is how you have things setup and the clients are not failing over to another server, we would need to know what clients you are running. Jeffrey Altman > > -Juha
smime.p7s
Description: S/MIME Cryptographic Signature
