On 10/18/07, Kostik Belousov <kostikbel_at_gmail.com> wrote: > On Wed, Oct 17, 2007 at 07:05:59AM -0500, Eric Anderson wrote: > > Kostik Belousov wrote: > > >On Tue, Oct 16, 2007 at 12:20:59PM +0200, Arjan van Leeuwen wrote: [...] > > > > > >Patch is wrong. Actually, it does put the dirrem to the proccessing twice > > >when xp != NULL. > > > > Yes, exactly why I said 'it doesn't fix the problem'. In fact, I > > actually did not post it to the list, and didn't intend for it to be > > posted. I was hoping for feedback for further examination. > > > > Kostik - do you have any ideas on what is going on here? Did you see > > the message in another thread that looked similar (it was regarding > > gjournal)? > > No, I have no idea. BTW, some further information from the people that > experience the problem could be helpful. For instance, > UFS1/UFS2 > size of the problematic fs/% of the space used > are quotas enabled in kernel/active for the fs ? > are softupdates on ? > what block number is reported as being freed twice ? is it always the same ? > what is the full fsck diagnostic after reboot ? Just want to add one more instance ;-) I have seen this kind of panic since 4.x, it does not happen very often but it often (not always) happens when the filesystem is full. The server in question is an i386 with local disk exported via nfs to ~20 clients. The filesystem was UFS1 and now UFS2 (but the underlying disk was changed to another raid box). Softupdate is turned on all the time, but not quota. The block in panic message does not the same. And I do full fsck after the panic (no background fsck). Some previous ddb and kgdb sessions can be found at: http://www.rafan.org/FreeBSD/panic/freeing_free_block/ Regards, Rong-En Fan > > The range of questions is so wide because I try to somewhat localize the > search field down from "anywhere". > >Received on Thu Oct 18 2007 - 13:04:10 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:19 UTC