From: "William L. Thomson Jr." <wltjr@gentoo.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: mdadm file system type check
Date: Sat, 17 Mar 2007 14:50:10 -0400 [thread overview]
Message-ID: <1174157410.17181.7.camel@wlt.obsidian-studios.com> (raw)
In-Reply-To: <45FC2F2B.7070506@tmr.com>
[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]
On Sat, 2007-03-17 at 13:10 -0500, Bill Davidsen wrote:
>
> First, please learn the difference between file system type (user data
> ON the device), and partition type (a byte in the partition table).
Which it's technical name would be a partition system ID. However older
versions of fdisk did refer to the t option as file system type.
http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/ref-guide/s1-filesystem-ext3-create.html
Given it's quite old and all newer docs refer to it mainly as partition
system id. At least that's what's shown in current fdisks
t change a partition's system id
Sorry for the miss-clarification. For the record, simply changing the
partitions system id from 83 -> fd allowed the commands that previously
failed to succeed and create the array.
> Second, mdadm cares not a bit about the partition type,
That would be my understanding of it so far, and experience with it.
> although some
> init scripts might.
FYI, this was a new install running on a livecd. So no init scripts were
involved.
> The reason it didn't work was because the partition
> was zero size or missing, and would not work regardless of the partition
> type.
Negative, it's one of the things I suggested for them to take a look at.
Even provided the snippet of the IRC log that I left out containing that
information in another post. To save you from having to dig it out. Here
it is again :)
wltjr: kingtaco|work: likely something else, partition off, wrong fs type, or etc
kingtaco|work: /dev/sda1 1 17 136521 83 Linux
kingtaco|work: /dev/sdb1 1 17 136521 83 Linux
Also I really would not be reporting this, or wasting any one's time if
it was not something abnormal. Thus reporting it, and my
miss-clarification of stuff surely did not help explain the situation :)
--
William L. Thomson Jr.
Gentoo/Java
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-17 18:50 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. [this message]
2007-03-17 1:39 ` berk walker
2007-03-17 9:27 ` Chris Lindley
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=1174157410.17181.7.camel@wlt.obsidian-studios.com \
--to=wltjr@gentoo.org \
--cc=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--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 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).