From: Phil Turmel <philip@turmel.org>
To: Pierre Beck <mail@pierre-beck.de>
Cc: freeone3000 <freeone3000@gmail.com>, NeilBrown <neilb@suse.de>,
linux-raid@vger.kernel.org
Subject: Re: Data Offset
Date: Wed, 13 Jun 2012 08:49:20 -0400 [thread overview]
Message-ID: <4FD88C50.1000104@turmel.org> (raw)
In-Reply-To: <4FD86179.1080209@pierre-beck.de>
On 06/13/2012 05:46 AM, Pierre Beck wrote:
[trim /]
> And DON'T run fsck early. Try mounting read-only, take a look at your
> data. Something bigger than chunksize, like a movie file, checksum some
> iso or smth. It should be intact. THEN run fsck. fsck cannot expect raid
> stripe reordering and worst case may cause damage (not that I heard of
> it happen, but inspecting data first is safe).
This is *dangerous* advice. Modern filesystems will replay their
journal even when mounted read-only. When attempting to determine the
member order, mounting the file system is *not* safe. And some
filesystems ignore the read-only status of the array, so that won't
avoid the problem.
fsck -n is the *only* safe way to automate the check. Hex dumps of
expected signature blocks is even better, but is difficult to automate.
HTH,
Phil
next prev parent reply other threads:[~2012-06-13 12:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 23:22 Data Offset freeone3000
2012-06-01 23:52 ` NeilBrown
2012-06-02 0:48 ` freeone3000
2012-06-04 3:35 ` NeilBrown
2012-06-04 18:26 ` Pierre Beck
2012-06-04 22:57 ` NeilBrown
2012-06-05 5:26 ` freeone3000
2012-06-05 5:44 ` NeilBrown
[not found] ` <CAFhY2CiDTMRSV2wFCMhT9ZstUkHkJS7E0p7SP-ssfqwaquo+0w@mail.gmail.com>
[not found] ` <20120610074531.65eaed81@notabene.brown>
[not found] ` <CAFhY2CgxkjH6JvJzvQt9XT0oawntK7YoTFqnXQJGzvqthD8XpQ@mail.gmail.com>
2012-06-13 9:46 ` Pierre Beck
2012-06-13 12:49 ` Phil Turmel [this message]
2012-06-13 17:56 ` Pierre Beck
2012-06-13 18:11 ` Phil Turmel
2012-06-13 18:22 ` Pierre Beck
2012-06-13 18:49 ` Piergiorgio Sartor
2012-06-20 3:56 ` freeone3000
2012-06-20 14:09 ` Pierre Beck
2012-06-25 6:25 ` NeilBrown
2014-02-24 11:22 ` wiebittewas
2014-02-24 21:38 ` NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2014-05-15 14:11 Data offset Patrik Horník
2014-05-15 22:07 ` NeilBrown
2014-05-16 0:41 ` Patrik Horník
2012-05-10 17:42 Data Offset Piergiorgio Sartor
2012-05-24 5:20 ` 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=4FD88C50.1000104@turmel.org \
--to=philip@turmel.org \
--cc=freeone3000@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mail@pierre-beck.de \
--cc=neilb@suse.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.