Re: wapbl_flush: current transaction too big to flush (was: WAPBL panic)

To: tech-kern%netbsd.org@localhost
Subject: Re: wapbl_flush: current transaction too big to flush (was: WAPBL panic)
From: mlelstv%serpens.de@localhost (Michael van Elst)
Date: Mon, 14 Dec 2015 14:04:56 +0000 (UTC)

manu%netbsd.org@localhost (Emmanuel Dreyfus) writes:

>4294967264 in 0xffffffe0 with suggests some int32 underrun. 

The field is 32bit in FFS1 and 64bit in FFS2.

>Is it possible to crash is not caused by a big transaction,
>but by a transaction whose block count went wrong?

Looks like it.

-- 
-- 
                                Michael van Elst
Internet: mlelstv%serpens.de@localhost
                                "A potential Snark may lurk in every tree."

Follow-Ups:
- Re: wapbl_flush: current transaction too big to flush (was: WAPBL panic)
  - From: Emmanuel Dreyfus

References:
- WAPBL panic
  - From: Emmanuel Dreyfus
- wapbl_flush: current transaction too big to flush (was: WAPBL panic)
  - From: Emmanuel Dreyfus

Prev by Date: wapbl_flush: current transaction too big to flush (was: WAPBL panic)
Next by Date: Re: wapbl_flush: current transaction too big to flush (was: WAPBL panic)
Previous by Thread: wapbl_flush: current transaction too big to flush (was: WAPBL panic)
Next by Thread: Re: wapbl_flush: current transaction too big to flush (was: WAPBL panic)
Indexes:

Home | Main Index | Thread Index | Old Index