> On 19. Jul 2018, at 03:54, Johnny Billquist <b...@softjar.se> wrote:
>
> Anyone seen this, or know what it's about?
Great, it took 6 months to trigger my assertion ...
This panic probably means the file contains unallocated inodes that
were only partially zeroed.
Please run "fsck -f" on this file system and look for messages
like "PARTIALLY ALLOCATED INODE".
> On NetBSD/vax, with 8.99.22 from today.
>
> Removing any file that has disk blocks allocated to it:
>
> [ 653.3285523] ufs_inactive: unlinked ino 50313 on "/home" has non zero size
> 0 or blocks 1ac0 with allerror 0
> [ 653.3484633] panic: ufs_inactive: dirty filesystem?
> [ 653.3788284] cpu0: Begin traceback...
> [ 653.3984724] panic: ufs_inactive: dirty filesystem?
> [ 653.4090004] Stack traceback :
> [ 653.4231115] Process is executing in user space.
> [ 653.4286045] cpu0: End traceback...
> Stopped in pid 39.1 (rm) at netbsd:vpanic+0xc5: pushl $0
>
>
> If a file is small enough to have all the data in the inode itself, rm
> survives fine.
We never hold file data in inodes, only short sysmlinks.
>
> Johnny
>
> --
> Johnny Billquist || "I'm on a bus
> || on a psychedelic trip
> email: b...@softjar.se || Reading murder books
> pdp is alive! || tryin' to stay hip" - B. Idol
--
J. Hannken-Illjes - hann...@eis.cs.tu-bs.de - TU Braunschweig (Germany)