Date: Thu, 02 Dec 2010 10:46:49 -0800 From: Kirk McKusick <mckusick@mckusick.com> To: David Rhodus <sdrhodus@gmail.com> Cc: Jeff Roberson <jroberson@chesapeake.net>, Michael Butler <imb@protected-networks.net>, freebsd-fs@freebsd.org Subject: PR kern/152605 Message-ID: <201012021846.oB2IknXX006899@chez.mckusick.com> In-Reply-To: <AANLkTing=GtHW8mg2CnNrXxVdKwBxTZpqFWibY4LsZM7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: David Rhodus <sdrhodus@gmail.com> > Date: Thu, 2 Dec 2010 12:33:35 -0500 > Subject: Re: How a full fsck screwed up my SU+J filesystem > To: Michael Butler <imb@protected-networks.net> > Cc: Kirk McKusick <mckusick@mckusick.com>, > Kostik Belousov <kostikbel@gmail.com>, current@freebsd.org > X-ASK-Info: Message Queued (2010/12/02 09:34:03) > X-ASK-Info: Confirmed by User (2010/12/02 09:35:13) > > Hello, what do you make of this PR report ? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/152605 > > This panic happens during bg-fsck every time. I have to boot into > single user-mode and do a fsck to correct. I have not seen this bug report yet. It would be helpful if you could identify which file is associated with inode 18, e.g., cd <filesystem that crashes> find . -x -inum 18 -ls Also, a transcript of the fsck that you run to clean up the mess so that I can see what is broken in the filesystem. Kirk McKusick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201012021846.oB2IknXX006899>