From: Chris Lindley <ferg@scotgate.org>
To: linux-raid@vger.kernel.org
Subject: Re: mdadm file system type check
Date: Sat, 17 Mar 2007 09:27:20 +0000 [thread overview]
Message-ID: <1174123640.12326.10.camel@scotgate> (raw)
In-Reply-To: <45FB46DA.7090307@panix.com>
What I think the OP is getting at is that MDADM will create an array
with partitions whose type is not set to FD (Linux Raid Auto), but are
perhaps 83.
The issue with that is that upon a reboot mdadm will not be able to
start the array. If you use MDADM to manually reassemble the array then
it will work fine. But until you reset the partition type to be FD, you
will have to run this step every time you reboot the machine.
Please note that I'm not disagreeing or agreeing whether the OP's idea
was a good idea, just trying to clarify the issue!
Cheers
Ferg
--
scotgate.org AIM#fergycool jabber#fergy IRC#Ferg MSN#fergycool
Climb up it, kayak down it + make sure it runs on GNU/Linux
"cease to exist, giving my goodbye, drive my car into the ocean,
you think I'm dead, but i sail away, on a wave of mutilation!"
On Fri, 2007-03-16 at 20:39 -0500, berk walker wrote:
>
> William L. Thomson Jr. wrote:
> > To whom it may concern,
> >
> > It seems mdadm does not check, warn, abort, or etc if a partition has
> > an incorrect file system type. This has come up for me on a few
> > occasions while building servers with software raid. On one occasion I
> > had a machine fully up and running on raid partitions that were ext3 not
> > linux auto raid/fd.
> >
> > If possible would really be nice if it could do a check for that. Since
> > one usually has to start over when they discover the problem and go to
> > correct it. Since raidtools is not deprecated, others migrating from it
> > on Gentoo are running into it at as well. At the present time mostly
> > developers. Really would not want users running into it :)
> >
> > Anyway if that could be addressed that would be great. Not sure if this
> > is the right place for this or not. If not please advise, thank you.
> >
> >
> Mdadm has no need to know or care about file systems. It exists on the
> hardware, /dev level, upon which file systems, if any, are built.
>
> b-
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-03-17 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 23:57 mdadm file system type check William L. Thomson Jr.
2007-03-17 1:30 ` Neil Brown
2007-03-17 2:42 ` William L. Thomson Jr.
2007-03-17 5:40 ` Neil Brown
2007-03-17 8:20 ` William L. Thomson Jr.
2007-03-17 18:10 ` Bill Davidsen
2007-03-17 18:50 ` William L. Thomson Jr.
2007-03-17 1:39 ` berk walker
2007-03-17 9:27 ` Chris Lindley [this message]
2007-03-17 23:08 ` Nix
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=1174123640.12326.10.camel@scotgate \
--to=ferg@scotgate.org \
--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).