From: Stefan *St0fF* Huebner <st0ff@gmx.net>
To: Keith Keller <kkeller@wombat.san-francisco.ca.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: using dd (or dd_rescue) to salvage array
Date: Tue, 07 Feb 2012 21:01:01 +0100 [thread overview]
Message-ID: <4F3182FD.9030602@gmx.net> (raw)
In-Reply-To: <20120207042407.GA5927@wombat.san-francisco.ca.us>
On 07.02.2012 05:24, Keith Keller wrote:
> On Mon, Feb 06, 2012 at 10:37:38PM +0100, Stefan *St0fF* Huebner wrote:
>> From the logical point of view those lost 8k would create bad data -
>> i.e. a filesystem problem OR simply corrupted data. That depends on
>> which blocks exactly are bad. If you were using lvm it could even be
>> worse, like broken metadata.
> FWIW, xfs_repair has spit out over 100k lines on stderr, but when I
> mounted before the repair (this is suggested if you need to replay the
> log), everything seemed intact. So I'm not yet sure what to make of
> things; perhaps it'll be fine, or perhaps I need to start over.
> (Alternatively, perhaps the next rsnapshot run will expose problems.)
>
>
> On Mon, Feb 06, 2012 at 10:38:27PM -0500, Phil Turmel wrote:
>> But, I reviewed the OEM documentation for the 7K3000 family, and they
>> clearly document support for the SCT ERC commands (para 9.18.1.2).
> If I'm reading the docs right, then the 5K3000 also supports them (if
> you're really cheap and can tolerate the slower speeds). At this point,
> if we're waiting till April for real ''enterprise'' drives, I can't see
> anything too bad about getting one or two of these and testing them out
> in my environment--the EARS drives are bad enough with my configuration
> that it's hard to imagine being any worse. (To be fair, I have to blame
> the 3ware 9550 controller a bit too; I have EARS drives on other 3ware
> controllers without all these issues.)
>
> --keith
>
>
>
Sounds promising. If you're really lucky, the blocks were freed by the
fs and nothing has gone...
Stefan
next prev parent reply other threads:[~2012-02-07 20:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 1:34 Please Help! RAID5 -> 6 reshapre gone bad Richard Herd
2012-02-07 2:15 ` Phil Turmel
[not found] ` <CAOANJV955ZdLexRTjVkQzTMapAaMitq5eqxP0rUvDjjLh4Wgzw@mail.gmail.com>
2012-02-07 2:57 ` Phil Turmel
2012-02-07 3:10 ` Richard Herd
2012-02-07 3:24 ` Keith Keller
2012-01-31 6:31 ` rebuild raid6 after two failures Keith Keller
2012-02-01 4:42 ` Keith Keller
2012-02-01 5:31 ` NeilBrown
2012-02-01 5:48 ` Keith Keller
2012-02-03 16:08 ` using dd (or dd_rescue) to salvage array Keith Keller
2012-02-04 18:01 ` Stefan /*St0fF*/ Hübner
2012-02-05 19:10 ` Keith Keller
2012-02-06 21:37 ` Stefan *St0fF* Huebner
2012-02-07 3:44 ` Keith Keller
2012-02-07 4:24 ` Keith Keller
2012-02-07 20:01 ` Stefan *St0fF* Huebner [this message]
2012-02-07 3:38 ` Please Help! RAID5 -> 6 reshapre gone bad Phil Turmel
2012-02-08 7:13 ` Stan Hoeppner
2012-02-07 3:04 ` Fwd: " Richard Herd
2012-02-07 2:39 ` NeilBrown
2012-02-07 3:10 ` NeilBrown
2012-02-07 3:19 ` Richard Herd
2012-02-07 3:39 ` NeilBrown
2012-02-07 3:50 ` Richard Herd
2012-02-07 4:25 ` NeilBrown
2012-02-07 5:02 ` Richard Herd
2012-02-07 5:16 ` NeilBrown
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=4F3182FD.9030602@gmx.net \
--to=st0ff@gmx.net \
--cc=kkeller@wombat.san-francisco.ca.us \
--cc=linux-raid@vger.kernel.org \
--cc=st0ff@npl.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.