From: "Eric Wood" <eric@interplas.com>
To: linux-raid@vger.kernel.org
Subject: does ext3 trample on mkraid superblocks and visa-versa?
Date: Wed, 10 Sep 2003 15:27:55 -0400 [thread overview]
Message-ID: <03dd01c377d1$a28c9be0$9100000a@intgrp.com> (raw)
In-Reply-To: 107a01c376fe$a29bdc00$9100000a@intgrp.com
I wanted to reword my previous email a little different to hopefully get a
response on this issue.
If I want to mirror an existing ext3 filesystem, then I would
"mkraid --really-force /dev/md0". Then /dev/hda1 would copy over to
/dev/hdc1 because /dev/hda1 is raid-disk 0 and /dev/hdc1 is raid-disk 1.
If I had cross up this priority number in the raidtab file, then mkraid
would have copied /dev/hdc1 over top of /dev/hda1 which would be a boo-boo.
Now as I understand it, mkraid adds a superblock at the far-end block of the
partition (whether or not that block is within the filesystem. It looks
like ext2 needs to be, but does ext3 need to be fsck'd and resized to
protect this block? Or does ext3 automatically see a raid superblock there
and help protect it without fck'ing and resizing. Or do you have to
tune2fs -o ^nojournal the filesystem back into an ext2 system because ext3,
journal block, mkraid, and raid superblocks step on each other's toes?
-Eric Wood
Eric Wood wrote:
> http://unthought.net/Software-RAID.HOWTO/Software-RAID.HOWTO-4.html#ss4.14
> 4. Sect. 4.14.14. Do I first have to convert from ext3 back to ext2?
> Since I use ext3 does this step still apply or does mkraid add the
> second superblock in an acceptable manor for ext3? Do I still have
> to resize2fs the md devices?
next prev parent reply other threads:[~2003-09-10 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 18:17 Converting a non-RAID RedHat System to run on Software RAID Eric Wood
2003-09-10 19:27 ` Eric Wood [this message]
2003-09-10 22:02 ` does ext3 trample on mkraid superblocks and visa-versa? dean gaudet
2003-09-11 17:33 ` Eric Wood
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='03dd01c377d1$a28c9be0$9100000a@intgrp.com' \
--to=eric@interplas.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).