Hello,
I have 2 servers (lets called them A and B). The A holds all of the read/write
volumes, all of these volumes are replicated to B (read only). The OpenAFS
services
run on both, in pretty much identical set-up. Both servers also have the
OpenAFS clients.
[A]<--
> The strange thing is, that when server B went down, pretty much everything
> went to halt,
> e.g. periodic downloads running on A would not be able to write to AFS
> anymore a the
> linux desktops would loose access to AFS.
No, there is no failover from reading the RW when the RO goes away.
Y
Am Montag 22 März 2010 10:43:51 schrieb Vladimir Konrad:
> Would you please give me few pointers on what to try to have AFS clients
> work even if the B goes down?
Create r/o replicas on A (and on the same vice partition), too.
The problem with your setup is that OpenAFS clients use the r/o path
Hello Dirk,
> Create r/o replicas on A (and on the same vice partition), too.
Will do.
> The problem with your setup is that OpenAFS clients use the r/o path to
> access
> data in replicated volumes, but you have put all your r/o replicas on one
> single machine, so you have created a single
> OpenAFS is not designed for automatic failover.
serverA volume.readonly -> serverB volume.readonly works automaticly
serverA volume.readonly -> serverB volume (readwrite) does _not_ fail
over automaticly
Harald.
___
OpenAFS-info mailing list
OpenAFS
