panic: ffx_valloc: dup alloc + SU+J + fsck

Kostik Belousov kostikbel at gmail.com
Tue Mar 1 23:03:30 UTC 2011


On Tue, Mar 01, 2011 at 11:03:17PM +0200, Nikos Vassiliadis wrote:
> Hello,
> 
> I am seeing this kernel panic on a su+j ufs. It seems that
> a su+j aware fsck cannot repair the file system, fsck corrects
> all fs-problems it finds but the kernel panics on the first
> write operation. The file system is corrected when a full fsck
> takes place. This fs lives on a virtual machine and I do have a
> snapshot of the fs in this problematic state in case someone
> wants to investigate further.
> 
> The panic:
> http://img135.imageshack.us/img135/1111/panicw.png
> 
> and a backtrace:
> http://img856.imageshack.us/img856/7516/65759196.png
> 
Note that if your fs somehow managed to get a corruption by whatever
means, then neither journaling not background fsck can repair it.
UFS panic that explicitely mentions fs corruption shall be always
followed by full fsck.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20110301/f49b7784/attachment.pgp


More information about the freebsd-fs mailing list