Re: panic: handle_written_inodeblock: live inodedep

2011-11-26 Thread Gleb Smirnoff
On Sat, Nov 26, 2011 at 10:05:25AM +0200, Kostik Belousov wrote: K> > Running HEAD with KMS patches from kib@, a 15th November K> > snapshot build from kms branch from ~kib/deviant2 repository. K> > The panic message and backtrace look unrelated to KMS, so, K> > I think my kernel can be considere

Re: panic: handle_written_inodeblock: live inodedep

2011-11-26 Thread Kostik Belousov
On Fri, Nov 25, 2011 at 09:08:27PM +0400, Gleb Smirnoff wrote: > Hi! > > Running HEAD with KMS patches from kib@, a 15th November > snapshot build from kms branch from ~kib/deviant2 repository. > The panic message and backtrace look unrelated to KMS, so, > I think my kernel can be considered a

panic: handle_written_inodeblock: live inodedep

2011-11-25 Thread Gleb Smirnoff
Hi! Running HEAD with KMS patches from kib@, a 15th November snapshot build from kms branch from ~kib/deviant2 repository. The panic message and backtrace look unrelated to KMS, so, I think my kernel can be considered a head from 15-th of November. Panic happened a couple of seconds after sys

panic "handle_written_inodeblock: live inodedep"

2001-11-26 Thread Peter Jeremy
Running -CURRENT from Sunday. Background: I had been building various ports and then deleting the work directories. Some time later, I unmounted that filesystem and ran fsck. The fsck reported about 190 files and 4 directories disconnected and reconnected them. Looking through lost+found, I re