Is there any way of determining *what* is causing this, based on the
information that I'm getting on the console? :(
dev=#da/0x20007, bno = 671547887, bsize = 16384, size = 16384, fs = /vm
panic: ffs_blkfree: bad size
mp_lock = 0201; cpuid = 2; lapic.id = 0600
boot() called on cpu#2
On Mon, Nov 28, 2005 at 06:16:38AM -0400, Marc G. Fournier wrote:
Is there any way of determining *what* is causing this, based on the
information that I'm getting on the console? :(
dev=#da/0x20007, bno = 671547887, bsize = 16384, size = 16384, fs = /vm
panic: ffs_blkfree: bad size
Let
= /vm
panic: ffs_blkfree: bad size
Let me take a wild guess and say unionfs ;-)
Not this time :)
I'm moving to unionfs clean systems, since I *really* want to get out of
4.x ... in the case above, its a brand new Dual Xeon, had something like
20 jails running on it ... 3x73G Seagate drives
of determining *what* is causing this, based on the
information that I'm getting on the console? :(
dev=#da/0x20007, bno = 671547887, bsize = 16384, size = 16384, fs = /vm
panic: ffs_blkfree: bad size
Let me take a wild guess and say unionfs ;-)
Kris
Marc G. Fournier Hub.Org
