Date: Mon, 3 Jan 2005 13:53:33 -0800 (PST) From: Arne "Wörner" <arne_woerner@yahoo.com> To: Pavel Merdine <freebsd-fs@merdin.com>, freebsd-fs@freebsd.org Subject: Re: dup alloc, please advice Message-ID: <20050103215333.32555.qmail@web41212.mail.yahoo.com> In-Reply-To: <505295882.20050104004342@merdin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> /kernel: mode = 040700, inum = 12, fs = /somemount > /kernel: panic: ffs_valloc: dup alloc > /kernel: > /kernel: syncing disks... 49 22 8 7 7 7 7 7 7 7 7 7 7 7 > > It happened just in 10 minutes after fsck. > Was fsck completed? If yes, what were the log messages/results? > There are lots of writes to that disk by many nfs clients at the > same times. > Not exactly the same time, I hope... :-)) > What should I do in such situations? > Have you tried: 1. Booting to single user mode and doing a "fsck /somemount" manually (I would like to see the results). 2. Halting the system gracefully (with halt or so) 3. Mounting just clean file systems (no -f or so; no soft updates (just for the beginning)) > FreeBSD 4.10-STABLE #0: Mon Jul 26 05:46:38 EDT 2004 > > By the way, sometimes I also get > /kernel: ufs_rename: fvp == tvp (can't happen) > in logs. > Might be an old inconsistency, too (if I remember right, you were the one, who liked to mount unclean fs :-)) ). -Arne __________________________________ Do you Yahoo!? Send a seasonal email greeting and help others. Do good. http://celebrity.mail.yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050103215333.32555.qmail>