Date: Fri, 04 Feb 2011 13:21:56 -0800 From: Doug Barton <dougb@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: ext2fs crash in -current (r218056) Message-ID: <4D4C6DF4.2060004@FreeBSD.org> In-Reply-To: <201102040759.51736.jhb@freebsd.org> References: <4D47B954.3010600@FreeBSD.org> <201102021704.04274.jhb@freebsd.org> <4D4B34F8.3040101@FreeBSD.org> <201102040759.51736.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/04/2011 04:59, John Baldwin wrote: > On Thursday, February 03, 2011 6:06:32 pm Doug Barton wrote: >> On 02/02/2011 14:04, John Baldwin wrote: >>> Err, this is a different panic than what you reported earlier. Your disk died >>> and spewed a bunch of EIO errors. I can look at the locking assertion failure >>> tomorrow, but this is a differnt issue. Even UFS needed a good bit of work to >>> handle disks dying gracefully. >> >> Can you defined "died" a bit? :-/ I just plugged it back in and it >> seems to be working Ok, but it's my backup disk so if I'm looking at a >> potential failure I'm a bit worried ... > > It's hard to say as the other errors have already scrolled off the screen. There weren't any other errors. I just trimmed the jpeg down to a more manageable level. > If you accidentally bumped the drive so that USB detached it then that would > have the same effect. I don't _think_ I did that, but it's not outside the realm of possibility. Thanks, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D4C6DF4.2060004>