[OpenAFS] Communication errors on volume operations
Derrick Brashear
shadow@gmail.com
Fri, 5 Dec 2008 12:38:08 -0500
------=_Part_18812_26823532.1228498688215
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Fri, Dec 5, 2008 at 7:53 AM, Bryn Divey <bryn@bengueladev.com> wrote:
> On Thu, 2008-12-04 at 16:17 -0500, Derrick Brashear wrote:
> > On Thu, Dec 4, 2008 at 10:34 AM, Matt Benjamin <matt@linuxbox.com>
> > wrote:
> > Hi Bryn,
> >
> > Is this a DAFS file server? If so, then probably a known
> > behavior, although I'm not certain it should be seen in 1.5.55
> > (Tom?) As you imply, the volume can in that case be salvaged
> > and then brought on-line (bos salvage -forceDAFS).
> >
> > It's not fixed in 1.5.55, and while the DAFS changes caused it it
> > happens in the non-DAFS case also ATM.
>
> Thanks for the replies.
>
> No, this isn't a DAFS server. As you've said, the salvage fixes it - I
> wanted to confirm that it's a known issue, as I couldn't find it in the
> tracker.
>
> On another note, does anyone know what the status around stable
> read-write disconnect is? Might it make 1.6? What is the proposed
> release timeline?
We hope to haveredwrite disconnected stable and with the remaining features
implemented (cache persistence across reboot so changes to be written back
persist) in time for 1.6.
The more likely bottleneck is currently getting the DAFS-related issues in
1.5 worked out.
Derrick
--
Derrick
------=_Part_18812_26823532.1228498688215
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><br><div class="gmail_quote">On Fri, Dec 5, 2008 at 7:53 AM, Bryn Divey <span dir="ltr"><<a href="mailto:bryn@bengueladev.com">bryn@bengueladev.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Thu, 2008-12-04 at 16:17 -0500, Derrick Brashear wrote:<br>
> On Thu, Dec 4, 2008 at 10:34 AM, Matt Benjamin <<a href="mailto:matt@linuxbox.com">matt@linuxbox.com</a>><br>
> wrote:<br>
> Hi Bryn,<br>
><br>
> Is this a DAFS file server? If so, then probably a known<br>
> behavior, although I'm not certain it should be seen in 1.5.55<br>
> (Tom?) As you imply, the volume can in that case be salvaged<br>
> and then brought on-line (bos salvage -forceDAFS).<br>
><br>
> It's not fixed in 1.5.55, and while the DAFS changes caused it it<br>
> happens in the non-DAFS case also ATM.<br>
<br>
</div>Thanks for the replies.<br>
<br>
No, this isn't a DAFS server. As you've said, the salvage fixes it - I<br>
wanted to confirm that it's a known issue, as I couldn't find it in the<br>
tracker.<br>
<br>
On another note, does anyone know what the status around stable<br>
read-write disconnect is? Might it make 1.6? What is the proposed<br>
release timeline?</blockquote><div><br>We hope to haveredwrite disconnected stable and with the remaining features implemented (cache persistence across reboot so changes to be written back persist) in time for 1.6. <br>
</div></div><br>The more likely bottleneck is currently getting the DAFS-related issues in 1.5 worked out.<br><br>Derrick<br><br><br clear="all"><br>-- <br>Derrick<br>
------=_Part_18812_26823532.1228498688215--