>>>>> "srivas" == srivas <[EMAIL PROTECTED]> writes:
srivas> *File* servers never have participated in any kind of quorum
srivas> stuff.
Yeah.....which does not stop AFS from choking when quorum goes away.
srivas> Database servers do, but they don't serve volumes. FWIW,
srivas> the pts and kas database servers do give out read-only info
srivas> even when not in quorum (pts added in 3.4). The
srivas> volume-location database servers will still not give out r/o
srivas> data out of quorum.
I hope that the pts changes will make it do what I need it to; We've
been waiting for R/O access out of quorum since 1993. Without R/O
access out of quorum, AFS is really unsuitable for widely distributed
production environments.
Your statement that the vlserver will not work the same way worries me;
what does that mean for clients of a machine (assume it's running all
services) that's out of quorum? Will they be able to reboot and still
get r/o AFS space?
The manpages say:
when the information in the VLDB is
inaccessible, the Cache Manager cannot retrieve files, even
if the File Server processes are working properly.
Does this mean that AFS will NOT work out of quorum for read/only
files at 3.4??
-Rens
