NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/60621 (panic: ufs_inactive: dirty filesystem?)



The following reply was made to PR kern/60621; it has been noted by GNATS.

From: "J. Hannken-Illjes" <hannken%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/60621 (panic: ufs_inactive: dirty filesystem?)
Date: Sun, 15 Nov 2026 14:32:10 +0000

 With this simple recipe I always get the panic "transaction too big...":
 
   dd if=/dev/zero of=file0 bs=1m count=45k
   /usr/sbin/fssconfig -c -v fss0 / /
   rm file0
 
 Using a persistent snapshot or no snapshot the "rm" succeeds.
 
 Unfortunately on next reboot "wapbl_replay" always succeeds and the
 "ufs_inactive" panic doesn't happen.  I remember seeing this panic
 some times with crashes while an unlinked snapshot was open.
 
 I'm quite sure this inode 61 is such an unlinked snapshot.  It was
 registered with "wapbl_register_inode" when its link count became zero
 while it was still open.  On reboot "wapbl_replay" finds it, truncates
 it to size zero and "ufs_inactive" panics.  As this inode now has
 size zero and block count 0xfffffffffffffec0 == -320 it looks like the
 the field i_blocks was too low, missing 320 disk blocks.
 
 Have to look deeper into wapbl if there should be a guarantee the number
 of allocated blocks and the inode field i_blocks are in sync when a
 transaction gets flushed.
 
 -- 
 J. Hannken-Illjes - hannken%netbsd.org@localhost
 



Home | Main Index | Thread Index | Old Index