From: Dennison Williams <evoltech@2inches.com>
To: linux-raid@vger.kernel.org
Subject: The effects of multiple layers of block drivers
Date: Thu, 10 Jan 2008 14:58:49 -0800 [thread overview]
Message-ID: <4786A329.90702@2inches.com> (raw)
Hello,
I am starting to dig into the Block subsystem to try and uncover the
reason for some data I lost recently. My situation is that I have
multiple block drivers on top of each other and am wondering how the
effectss of a raid 5 rebuild would affect the block devices above it.
The layers are raid 5 -> lvm -> cryptoloop. It seems that after the
raid 5 device was rebuilt by adding in a new disk, that the cryptoloop
doesn't have a valid ext3 partition on it.
As a raid device re-builds is there ant rearranging of sectors or
corresponding blocks that would effect another block device on top of it?
Sincerely,
Dennison Williams
next reply other threads:[~2008-01-10 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 22:58 Dennison Williams [this message]
2008-01-11 1:45 ` The effects of multiple layers of block drivers Neil Brown
2008-01-11 8:38 ` Nagilum
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=4786A329.90702@2inches.com \
--to=evoltech@2inches.com \
--cc=linux-raid@vger.kernel.org \
/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).