[OpenAFS] Re: another MacOS cache manager wedging
Sun, 31 Jan 2010 11:28:44 -0500
On Sat, Jan 30, 2010 at 3:06 PM, Adam Megacz <firstname.lastname@example.org> wrote:
> Derrick Brashear <email@example.com> writes:
>> ** Cache entry @ 0x45e0f004 for 18.104.22.168 [dynroot]
>> =A0 =A0 locks: (writer_waiting, write_locked(pid:2870 at:54), 2 waiters)
>> I don't even have to look at this one. 54 is FetchStatus. Oddly, it's
>> dynroot, so there's something off here.
> Here's another:
> Lock afs_xserver status: (none_waiting, 1 read_locks(pid:0))
> Lock afs_xvcb status: (writer_waiting, write_locked(pid:0 at:273), 2
> ** Cache entry @ 0x45dee6c4 for 200.536870919.44.36878 [megacz.com]
> =A0 =A0locks: (none_waiting, write_locked(pid:10589 at:54))
Which server is 536870919 on, and why (from the client's perspective)
would it not be answering?