From: Doug Ledford <dledford@redhat.com>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: Stan Hoeppner <stan@hardwarefreak.com>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: RFC swap over raid1
Date: Fri, 02 Aug 2013 12:35:43 -0400 [thread overview]
Message-ID: <51FBDFDF.70008@redhat.com> (raw)
In-Reply-To: <CAH3kUhELqOF3kruP1j94g3Yd4PwKL91rgUjoLDS=CTK5ieBuhg@mail.gmail.com>
On 08/02/2013 11:59 AM, Roberto Spadim wrote:
> nice good explanations thanks
>
> one more doubt....
> filesystem handle bad blocks
> md handle bad blocks
>
> what happen when i have a filesystem over md?
> does md report badblocks to filesystem?
>
If md can not repair the block and it is unable to get the data from
some other device in the array, then and only then will it report the
error back up to the filesystem layer on top of it. In that case, the
filesystem will see the error and execute whatever the default behavior
on error is, which is different from filesystem to filesystem, but in
the past has commonly been to force the filesystem immediately into a
read-only mode so no further damage can happen and attempts at repair
can be made in rescue mode.
next prev parent reply other threads:[~2013-08-02 16:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 22:11 RFC swap over raid1 Roberto Spadim
2013-08-01 23:04 ` Doug Ledford
2013-08-02 2:01 ` Roberto Spadim
2013-08-02 7:46 ` Stan Hoeppner
2013-08-02 14:21 ` Roberto Spadim
2013-08-02 15:40 ` Doug Ledford
2013-08-02 15:59 ` Roberto Spadim
2013-08-02 16:35 ` Doug Ledford [this message]
2013-08-02 16:40 ` Roberto Spadim
2013-08-02 16:50 ` Doug Ledford
2013-08-02 17:29 ` Roberto Spadim
2013-08-02 17:35 ` Doug Ledford
2013-08-02 17:38 ` Roberto Spadim
2013-08-02 18:26 ` keld
2013-08-02 18:39 ` Roberto Spadim
2013-08-02 21:31 ` Keld Jørn Simonsen
2013-08-02 15:21 ` Doug Ledford
2013-08-02 1:59 ` Brad Campbell
2013-08-02 2:02 ` Roberto Spadim
2013-08-02 2:18 ` Brad Campbell
2013-08-02 2:21 ` Roberto Spadim
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=51FBDFDF.70008@redhat.com \
--to=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=roberto@spadim.com.br \
--cc=stan@hardwarefreak.com \
/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.