[OpenAFS] AFS 'fs checkv' and client daemon, volume renames not seen by clients
Derrick Brashear
shadow@gmail.com
Fri, 21 Sep 2007 15:17:37 -0400
------=_Part_18100_15876446.1190402257056
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 9/21/07, Kim Kimball <dhk@ccre.com> wrote:
>
> I thought that the AFS client was supposed to do the equivalent of an
> 'fs checkv' on a timed thread, every hour.
I think it's 2 hours.
> I've recently seen clients not notice a change in volumeID:name mapping
> for more than two days, and an 'fs checkv' corrected the problem
> instantly.
linux? get a task listing with alot sysrq t?
------=_Part_18100_15876446.1190402257056
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><br><div><span class="gmail_quote">On 9/21/07, <b class="gmail_sendername">Kim Kimball</b> <<a href="mailto:dhk@ccre.com">dhk@ccre.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I thought that the AFS client was supposed to do the equivalent of an<br>'fs checkv' on a timed thread, every hour.</blockquote><div><br>I think it's 2 hours. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>I've recently seen clients not notice a change in volumeID:name mapping<br>for more than two days, and an 'fs checkv' corrected the problem instantly.</blockquote><div><br>linux? get a task listing with alot sysrq t?
<br> <br></div><br></div><br>
------=_Part_18100_15876446.1190402257056--