[OpenAFS] replication issues 1.3.85

Sat, 23 Jul 2005 21:06:46 -0700

This is a multi-part message in MIME format.

------_=_NextPart_001_01C59005.1B9D4487
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

   Hrmm ok I though the way the cache manager worked was to always =
favored RO copies to begin with. So what you are saying is if I create =
the volume put the data into it then mount it with the .readonly =
extenstion this will solve the issue I am having?

I feel like I am still somehow missing a step here. Do I need to mount =
the volume readonly on each of the servers? I didnt/dont think its =
possible to have the same mountpoint name on more then one server. Feels =
like Im right there just mising the final step in all this =
documentation.

What I am needing to accomplish is a RO volume that will be accesible at =
all times even if one of the servers suddenly dies.

Thank you for the help,

Jacob L.

-----Original Message-----
From: openafs-info-admin@openafs.org on behalf of Jeffrey Altman
Sent: Fri 7/22/2005 4:48 PM
Cc: openafs-info@openafs.org
Subject: Re: [OpenAFS] replication issues 1.3.85
=20
Esther Filderman wrote:
> Since RW data is static, RO data is not used to "cover" for =
unavailable RW data.

Esther meant to say:

Since the data stored in a RW volume is volatile, a RO volume cannot be
used to provide automatic failover.  If a RO volume was used to as a
failover for a RW volume that suddenly became unavailable, you would
risk suffering data corruption.

Jeffrey Altman

------_=_NextPart_001_01C59005.1B9D4487
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">
<TITLE>RE: [OpenAFS] replication issues 1.3.85</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Hello,<BR>
<BR>
&nbsp;&nbsp; Hrmm ok I though the way the cache manager worked was to =
always favored RO copies to begin with. So what you are saying is if I =
create the volume put the data into it then mount it with the .readonly =
extenstion this will solve the issue I am having?<BR>
<BR>
I feel like I am still somehow missing a step here. Do I need to mount =
the volume readonly on each of the servers? I didnt/dont think its =
possible to have the same mountpoint name on more then one server. Feels =
like Im right there just mising the final step in all this =
documentation.<BR>
<BR>
What I am needing to accomplish is a RO volume that will be accesible at =
all times even if one of the servers suddenly dies.<BR>
<BR>
Thank you for the help,<BR>
<BR>
Jacob L.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: openafs-info-admin@openafs.org on behalf of Jeffrey Altman<BR>
Sent: Fri 7/22/2005 4:48 PM<BR>
Cc: openafs-info@openafs.org<BR>
Subject: Re: [OpenAFS] replication issues 1.3.85<BR>
<BR>
Esther Filderman wrote:<BR>
&gt; Since RW data is static, RO data is not used to &quot;cover&quot; =
for unavailable RW data.<BR>
<BR>
Esther meant to say:<BR>
<BR>
Since the data stored in a RW volume is volatile, a RO volume cannot =
be<BR>
used to provide automatic failover.&nbsp; If a RO volume was used to as =
a<BR>
failover for a RW volume that suddenly became unavailable, you would<BR>
risk suffering data corruption.<BR>
<BR>
Jeffrey Altman<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C59005.1B9D4487--