From: Boszormenyi Zoltan <zboszor@mail.externet.hu>
To: linux-kernel@vger.kernel.org
Subject: Ext2/Ext3 partition label abuse
Date: Fri, 08 Mar 2002 10:49:00 +0100 [thread overview]
Message-ID: <3C88890C.6010303@mail.externet.hu> (raw)
Hi!
I have a RedHat 7.2 machine installed from scratch.
Recently I installed RedHat 7.2 on another machine
that has two harddisks (/dev/hda and /dev/hdc)
The second is in a removable bay.
Linux was installed on /dev/hdc.
My main machine also has a hdd bay (/dev/hdc) and I have
put the new machine's removable hdd into the main one
and booted up. (I had to copy some files and no network
between the machines.)
On boot I had strange errors that said that this and that
partitions cannot be found. I observed the following.
The / partition contains the main machine's data from /dev/hda2
although the mount command lists / as mounted from /dev/hdcX.
Every other partitions are mounted from /dev/hdc.
The problem is that /etc/fstab as used by RedHat, lists the partition
by LABEL=/mountpoint which labels can be found on both
/dev/hda and /dev/hdc.
The /proc/partitions "file" lists the partitions in disk-reversed order,
e.g.:
/dev/hdc1 ....
...
/dev/hdc10 ...
/dev/hda1 ...
...
/dev/hda9 ...
Is there a way to fix this? Yes there is: vendors should not use
LABEL=XXX method in /etc/fstab. Either use the proper
device/partition or the UUID. The downside is that fsck messages
would not be as pretty-printed as now. Or maybe the partitions
should not be registered in disk-reversed order...
Best regards,
Zoltán Böszörményi
next reply other threads:[~2002-03-08 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 9:49 Boszormenyi Zoltan [this message]
2002-03-08 14:33 ` Ext2/Ext3 partition label abuse Guest section DW
2002-03-08 18:02 ` Mike Fedyk
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=3C88890C.6010303@mail.externet.hu \
--to=zboszor@mail.externet.hu \
--cc=linux-kernel@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