> > i couldn't agree with this more. this is one of the core problems
> > we've attempted to address as we deploy afs worldwide across our
> > internal wan.
>
> Would the availability of read-only access to database servers without
> quorum alter your statements?
This would be incredibly cool, ...
> In other words, are y'all (those of you who are, that is) suggesting
> transparent cross-cell volumes as a mechanism for dealing with this
> database problem? Which, if it didn't exist, would prompt you to simply
> use a single cell?
... on the other hand the fact that setuid-ignoring is a per-cell
and not also a per-volume (or at least, per-fileserver) flag still
bites.
John
- database server behavior during network parti... rick
- Re: database server behavior during netw... Rens Troost
- Re: database server behavior during ... Marcus Watts
- database server behavior during network ... Mark H. Linehan (8-863-7860)
- Re: database server behavior during ... Michael Niksch
- Re: database server behavior during netw... Mark Giuffrida
- Re: database server behavior during ... Rens Troost
- Re: database server behavior during ... Perry E. Metzger
- Re: database server behavior dur... Bruce Howard
- Re: database server behavior... Lyle_Seaman
- Re: database server beh... John Hascall
- Re: database server... Michael Niksch
- Re: database server beh... Rens Troost
- Re: database server beh... Perry E. Metzger
- Re: database server beh... Paul Vickers
- Re: database server beh... Michael Niksch
- Re: database server behavior during netw... Joseph W. Sieczkowski
