From: NeilBrown <neilb@suse.de>
To: Oliver Schinagl <oliver+list@schinagl.nl>
Cc: linux-raid@vger.kernel.org
Subject: Re: Small short question Was: Re: Recovering from the kernel bug, Neil?
Date: Thu, 20 Sep 2012 12:22:18 +1000 [thread overview]
Message-ID: <20120920122218.07f89443@notabene.brown> (raw)
In-Reply-To: <50531A52.7060205@schinagl.nl>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
On Fri, 14 Sep 2012 13:51:46 +0200 Oliver Schinagl <oliver+list@schinagl.nl>
wrote:
> Since I had only one valid device to check with etc, I assume that if
> fsck -n -f /dev/md2 runs sucessfully, it is 100% safe to assume the
> array is perfectly healthy?
I might be a bit late here but....
No, not 100% safe.
I would at least mount the filesystem and have a look around - take a random
sample and see if it all looks credible. If it does then that is as good as
it gets.
>
> E.g. it should be perfectly safe to mdadm --zero-superblock on /dev/sda6
> and add it to /dev/md2 (missing /dev/sdb6)?
>
> I know technically this all works out fine, and the bug shouldn't have
> broken anything in that regard. Or is it absolutly recommended to simply
> create a new array, with a new FS on it, and copy all data over
> (Logically also with /dev/md2, /dev/sda6 missing and later adding sdb6)?
Creating a new array shouldn't be necessary. In general I would avoid
copying data when convenient.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-09-20 2:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 13:56 Recovering from the kernel bug Oliver Schinagl
2012-09-09 20:22 ` Recovering from the kernel bug, Neil? Oliver Schinagl
2012-09-09 23:08 ` NeilBrown
2012-09-10 8:44 ` Oliver Schinagl
2012-09-11 6:16 ` NeilBrown
2012-09-14 10:07 ` Oliver Schinagl
2012-09-14 11:51 ` Small short question Was: " Oliver Schinagl
2012-09-14 16:43 ` Small short question Peter Grandi
2012-09-14 20:19 ` Oliver Schinagl
2012-09-20 2:22 ` NeilBrown [this message]
2012-09-20 17:05 ` Small short question Was: Re: Recovering from the kernel bug, Neil? Oliver Schinagl
2012-09-20 17:49 ` Chris Murphy
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=20120920122218.07f89443@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=oliver+list@schinagl.nl \
/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).