[2171] in SIPB-AFS-requests
[daemon@ATHENA.MIT.EDU : quorum? (was Re: Intermediate Caching)]
daemon@ATHENA.MIT.EDU (jweiss@MIT.EDU)
Thu Oct 26 17:58:14 1995
From: jweiss@MIT.EDU
Date: Thu, 26 Oct 1995 17:53:58 -0400
To: afsdev@MIT.EDU, sipb-afsreq@MIT.EDU
Assuming this (that 3.4 servers will give out prdb info w/o a sync
site) is true, it means that running 3.4 on our servers (once it is
stable, of course) might make two DB server cells less dangerous.
Jonathon
------- Forwarded transaction
[4190] daemon@ATHENA.MIT.EDU (srivas@transarc.com) Info-AFS_Redistribution 10/25/95 16:32 (15 lines)
Subject: quorum? (was Re: Intermediate Caching)
Date: Wed, 25 Oct 1995 14:39:02 EDT
From: srivas@transarc.com
To: rens@imsi.com
Cc: Info-AFS@transarc.com, bb+transarc.clippings@transarc.com
>Can't do this until servers can continue to serve Read-Only volumes
>while partitioned from quorum. Waiting..... :)
*File* servers never have participated in any kind of quorum stuff.
Database servers do, but they don't serve volumes. FWIW, the pts and
kas database servers do give out read-only info even when not in quorum
(pts added in 3.4). The volume-location database servers will still not
give out r/o data out of quorum.
--[4190]--
------- End forwarded transaction