Re: panic: ffs_valloc: dup alloc

[Brett Lymn <blymn%baesystems.com.au@localhost>]

On Sun, Mar 21, 2010 at 04:49:05PM -0400, Steven Bellovin wrote:
> 
> > That sounds like maybe the problem is not on the suspend side but on
> > the resume side, that is, that stuff is being written out before (some
> > layer of) the disk subsystem is ready to go again. With vanilla FFS
> > such writes should be synchronous so it should be (relatively) easy to
> > figure out what's going on. Do you feel like trying out dtrace? :-)
> 
> If you'd asked a week ago, sure; now, I don't have the time.

I need to update my -current to something more recent...

>  I don't think it's just named pipes anymore; the last crash I had
> did pretty horrific things to the file system, probably because some
> processes were busy creating files at the time I suspended.  >

I was seeing the corruption on plain files, mostly duplicate
allocations or freeing a free frag.  It looks to me like the kernel
thinks that the FS operation has been committed to disk but the bits
on the physical media have not changed.

-- 
Brett Lymn
"Warning:
The information contained in this email and any attached files is
confidential to BAE Systems Australia. If you are not the intended
recipient, any use, disclosure or copying of this email or any
attachments is expressly prohibited.  If you have received this email
in error, please notify us immediately. VIRUS: Every care has been
taken to ensure this email and its attachments are virus free,
however, any loss or damage incurred in using this email is not the
sender's responsibility.  It is your responsibility to ensure virus
checks are completed before installing any data sent in this email to
your computer."