[OpenAFS] Re: CopyOnWrite failure, leading to volume salvage

Derrick Brashear shadow@gmail.com
Thu, 27 Sep 2012 11:39:10 -0400

On Thu, Sep 27, 2012 at 11:07 AM, Andrew Deason <adeason@sinenomine.net> wrote:
> On Thu, 27 Sep 2012 10:45:45 +0100
> Dameon Wagner <dameon.wagner@it.ox.ac.uk> wrote:
>> #---8<-----------------------------------------------------------------
>> CopyOnWrite failed: Partition /vicepa that contains volume 536874907 may be out of free inodes(errno = 2)
>> Alloc_NewVnode: partition /vicepa idec 9492608003410095 failed
>> Volume : 536874907 vnode = 592047 Failed to create inode: errno = 2
>> #---8<-----------------------------------------------------------------
>> Troubleshooting showed that there was no shortage of inodes, so that
>> wasn't the underlying issue (I read it as only a likely suggestion, or
>> one possible cause).
> It's not going to be that with that errno, I don't think. If there was
> an actual error in creating the relevant file due to space issues you
> would probably actually see ENOSPC. ENOENT is probably something just
> wrong with the volume metadata.
> If the linktable file somehow got suddenly deleted (or maybe
> corrupted?), I think you'd get this. That would also cause the idec to
> fail, and it would be something the salvager will correct (possibly
> silently). I'm guessing, though; hard to say without being able to see
> what was in /vicepX at the time.

strace output from the salvager (run by hand rather than via bos)
may actually shed some light on what call is failing and
thus what is likely corrupt.