From: Theodore Ts'o <tytso@mit.edu>
To: Brian Candler <B.Candler@pobox.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Kernel panic from corrupt journal
Date: Fri, 31 Aug 2012 13:46:54 -0400 [thread overview]
Message-ID: <20120831174654.GA6342@thunk.org> (raw)
In-Reply-To: <20120831085307.GC17438@nsrc.org>
On Fri, Aug 31, 2012 at 09:53:07AM +0100, Brian Candler wrote:
>
> You're quite right: yesterday I did see some I/O errors after I had mounted
> the filesystem using -o ro,noload.
>
> So this morning I ran
>
> dd if=/dev/sda8 of=/dev/null bs=1024k
>
> and it completed without a problem. And then I found I was able to mount the
> filesystem just fine!
>
> So this is definitely a hardware problem; it's just I didn't realise I/O
> errors could cause kernel panics as well as EIO.
Well, it's not *supposed* to cause kernel panics. If you can get a
stack trace in the future under similar circumstnaces, definitely
capture it (using a digital camera if you don't have a better way,
such as a network console or a serial console). Even if it's not an
ext4 bug, but I'm happy to to try to route the bug report to the
appropriate kernel developer or mailing list.
> I am currently refreshing my most recent backup of this drive, and I'll
> replace it ASAP.
The drive *might* be OK at this point. If you are willing to run a
full read/write test on the drive, and it shows no problem, it might
be worth trying to put it back in production (especially if you are
keeping regular backups); if it fails a second time, then it's
definitely time to replace it. It's really a question of how much the
cost of a new drive is worth compared to your time and the value of
your data in case of a second failure.
Or maybe you could a buy a second 500G drive, and set up software RAID
1 using the md device. This will give you protection if either of the
two drive fails, as well as giving you speed boost for reads.
Cheers!
- Ted
prev parent reply other threads:[~2012-08-31 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 9:22 Kernel panic from corrupt journal Brian Candler
2012-08-31 5:53 ` Theodore Ts'o
[not found] ` <20120831085307.GC17438@nsrc.org>
2012-08-31 17:46 ` Theodore Ts'o [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120831174654.GA6342@thunk.org \
--to=tytso@mit.edu \
--cc=B.Candler@pobox.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).