From: Eric Sandeen <sandeen@redhat.com>
To: "Bill Huey (hui)" <bill.huey@gmail.com>
Cc: Theodore Tso <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: ext4 corruption
Date: Mon, 28 Feb 2011 09:01:54 -0600 [thread overview]
Message-ID: <4D6BB8E2.7080106@redhat.com> (raw)
In-Reply-To: <AANLkTimcKiKgKTVft9N+OVHd5-N+-AscSoimdOfkoBt9@mail.gmail.com>
On 2/26/11 5:13 AM, Bill Huey (hui) wrote:
> Theodore,
>
> I did run fsck.ext4 on the file system. It cleared a bunch of errors
> and but it's still showing various problems.
>
> Another log of the file system. USB->SATA problems ?
> ---------------------------------
>
> Feb 22 19:23:31 finfin kernel: [ 2.402463] sd 6:0:0:0: [sdb]
> 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
> Feb 22 19:23:31 finfin kernel: [ 2.403585] sd 6:0:0:0: [sdb] Write
> Protect is off
> Feb 22 19:23:31 finfin kernel: [ 2.405920] sdb:
> Feb 22 19:23:31 finfin kernel: [ 2.819633] sdb1
> Feb 22 19:23:31 finfin kernel: [ 2.821592] sd 6:0:0:0: [sdb]
> Attached SCSI disk
> Feb 22 19:27:40 finfin kernel: [ 263.857108] sdb: sdb1
> Feb 22 20:03:18 finfin kernel: [ 2402.182269] EXT4-fs (sdb1): mounted
> filesystem with ordered data mode. Opts: (null)
> Feb 25 03:49:40 finfin kernel: [203184.800029] EXT4-fs (sdb1):
> warning: mounting fs with errors, running e2fsck is recommended
this must not have been post-fsck, if it still is mounting with errors...?
...
> Feb 25 21:51:47 finfin kernel: [59900.021575] EXT4-fs (sdb1): mounted
> filesystem with ordered data mode. Opts: (null)
> Feb 26 02:19:27 finfin kernel: [75959.826438] sd 6:0:0:0: [sdb]
> Unhandled error code
> Feb 26 02:19:27 finfin kernel: [75959.826444] sd 6:0:0:0: [sdb]
> Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> Feb 26 02:19:27 finfin kernel: [75959.826450] sd 6:0:0:0: [sdb] CDB:
> Read(10): 28 00 ac 44 00 3f 00 00 08 00
and this does indeed look like storage problems, ext4 problems are
probably secondary.
-Eric
next prev parent reply other threads:[~2011-02-28 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 10:16 ext4 corruption Bill Huey (hui)
2011-02-26 11:10 ` Theodore Tso
2011-02-26 11:13 ` Bill Huey (hui)
2011-02-26 11:16 ` Bill Huey (hui)
2011-02-28 4:43 ` Ted Ts'o
2011-02-28 20:18 ` Bill Huey (hui)
2011-02-28 20:30 ` Bill Huey (hui)
2011-02-28 22:55 ` Ted Ts'o
2011-02-28 23:45 ` Bill Huey (hui)
2011-02-28 15:01 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-06 3:59 Micah Anderson
2011-06-06 4:19 ` Ted Ts'o
2011-06-06 17:11 ` micah anderson
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=4D6BB8E2.7080106@redhat.com \
--to=sandeen@redhat.com \
--cc=bill.huey@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).