Re: panic when removing a file in current

[Johnny Billquist <bqt%softjar.se@localhost>]

On 2018-07-19 06:12, maya%netbsd.org@localhost wrote:
> On Thu, Jul 19, 2018 at 03:54:17AM +0200, Johnny Billquist wrote:
> > Anyone seen this, or know what it's about?
> >
> > 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.
> >
> >    Johnny
> >
> > --
> > Johnny Billquist                  || "I'm on a bus
> >                                    ||  on a psychedelic trip
> > email: bqt%softjar.se@localhost             ||  Reading murder books
> > pdp is alive!                     ||  tryin' to stay hip" - B. Idol
>
> The only recent relevant-looking change is
> https://mail-index.netbsd.org/source-changes-hg/2018/07/19/msg002880.html

I'll check around this. But the panic is happening in 
ufs/ufs/ufs_inode.c, and that change was in ufs/ffs/ffs_vfsops.c. But 
was also suggested by Paul, so... I'll get back with results later.

> Cool that someone is very up-to-date on vax :-)

It's even worse. This is on a real VAX 8650... Very possibly the 
physically largest thing NetBSD that anyone is trying to run NetBSD 
on... :-)

  Johnny
--
Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
email: bqt%softjar.se@localhost             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol