Re: kern/54504: -9/-current WAPBL panic: current transaction too big to flush

[Joerg Sonnenberger <joerg%bec.de@localhost>]

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

From: Joerg Sonnenberger <joerg%bec.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: jdolecek%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
	kardel%netbsd.org@localhost
Subject: Re: kern/54504: -9/-current WAPBL panic: current transaction too big
 to flush
Date: Fri, 30 Aug 2019 15:49:54 +0200

 On Fri, Aug 30, 2019 at 05:30:02AM +0000, David Holland wrote:
 > The following reply was made to PR kern/54504; it has been noted by GNATS.
 > 
 > From: David Holland <dholland-bugs%netbsd.org@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc: 
 > Subject: Re: kern/54504: -9/-current WAPBL panic: current transaction too big
 >  to flush
 > Date: Fri, 30 Aug 2019 05:25:10 +0000
 > 
 >  On Thu, Aug 29, 2019 at 09:00:00AM +0000, kardel%netbsd.org@localhost wrote:
 >   > WAPBL panics when attempting to delete big files as the transaction
 >   > log size is insufficient. On reboot the subsequent mount will also
 >   > panic when attempting the re-play the log.
 >  
 >  I thought this had been fixed, or at least bodged around, some time
 >  ago. Has it regressed?
 
 Not exactly. The issue we fixed last time was removal of huge sparse
 files. This case is different in that the log space necessary for
 removal is linear in the size of the filesystem.
 
 Joerg