From: Mike Fedyk <mfedyk@matchmail.com>
To: Guest section DW <dwguest@win.tue.nl>
Cc: Boszormenyi Zoltan <zboszor@mail.externet.hu>,
linux-kernel@vger.kernel.org
Subject: Re: Ext2/Ext3 partition label abuse
Date: Fri, 8 Mar 2002 10:02:57 -0800 [thread overview]
Message-ID: <20020308180257.GG28141@matchmail.com> (raw)
In-Reply-To: <3C88890C.6010303@mail.externet.hu> <20020308143345.GA13406@win.tue.nl>
In-Reply-To: <20020308143345.GA13406@win.tue.nl>
On Fri, Mar 08, 2002 at 03:33:45PM +0100, Guest section DW wrote:
> On Fri, Mar 08, 2002 at 10:49:00AM +0100, Boszormenyi Zoltan wrote:
>
> [I had two disks with the same labels on one machine and that caused
> problems with booting]
>
> Yes, if you have an fstab file that says: mount the filesystem with
> label "ROOTDISK" on /, and then come with two filesystems that both are
> labeled "ROOTDISK", then it is hardly surprising when problems arise.
> The same will happen if you use UUID instead of label but created the
> other disk by copying the first using dd.
>
> You can change fstab for example with an editor.
> You can change labels for example with the e2label utility.
>
> Labels have an advantage for example when you add or remove a SCSI disk:
> the label stays the same but the disks are renumbered.
> Also when you add or remove partitions, causing a renumbering.
> Using UUID is slightly more stable, slightly less user-friendly.
>
> Attaching a significance to the order of items in /proc/partitions
> is a bad idea.
It would be nice if the raid code could do that with drive serial numbers...
next prev parent reply other threads:[~2002-03-08 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 9:49 Ext2/Ext3 partition label abuse Boszormenyi Zoltan
2002-03-08 14:33 ` Guest section DW
2002-03-08 18:02 ` Mike Fedyk [this message]
2002-03-08 18:24 ` H. Peter Anvin
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=20020308180257.GG28141@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=dwguest@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=zboszor@mail.externet.hu \
/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.