Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Jul 2001 14:00:03 -0700 (PDT)
From:      Ian Dowse <iedowse@maths.tcd.ie>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: i386/29045: Heavy disk usage causes panic in ffs_blkfree 
Message-ID:  <200107172100.f6HL03s82249@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/29045; it has been noted by GNATS.

From: Ian Dowse <iedowse@maths.tcd.ie>
To: Bill Moran <wmoran@iowna.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: i386/29045: Heavy disk usage causes panic in ffs_blkfree 
Date: Tue, 17 Jul 2001 21:51:30 +0100

 In message <200107171753.f6HHrPd52978@freefall.freebsd.org>, Bill Moran writes:
 >
 >Under heavy load, panics occur in the filesystem code. The panics apparently r
 >esult in some sort of subtle corruption to the filesystem that then results in
 > an increased chance of further panics.
 
 It's always difficult to tell if these panics are caused by a
 hardware/driver fault, or by filesystem bugs. Could you try printing
 out some more information including the contents of the free block
 bitmap from frame 2 on the stack - i.e. something like
 
 	frame 2
 	p fs
 	p *fs
 	p fs->fs_fpg
 	p bp->b_data
 	p cg
 	p cgp
 	p *cgp
 	p bno
 	p blksfree
 	p blksfree[0]@(fs->fs_fpg/8)
 
 A good test for hardware/driver faults is to take some large
 directory tree that does not change, especially one with lots of
 huge files, and run
 
 	find /whatever -type f -print0 |xargs -0 md5 > /tmp/md5.1
 	find /whatever -type f -print0 |xargs -0 md5 > /tmp/md5.2
 	find /whatever -type f -print0 |xargs -0 md5 > /tmp/md5.3
 
 etc while the system is under heavy load. Then diff the /tmp/md5.X
 files to see if anything has changed. You should try this with
 trees on different disks in case there is a driver/disk dependent
 corruption problem. Also try leaving quite a long gap between
 running the finds; data could be getting corrupted as it sits in
 the buffer cache.
 
 Ian

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107172100.f6HL03s82249>