public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@soleranetworks.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: e2label suggestions
Date: Tue, 28 Mar 2006 14:48:50 -0700	[thread overview]
Message-ID: <4429AF42.1090101@soleranetworks.com> (raw)


e2label takes as parms:

e2label <device name> <mount point>

What's useless about this is the association of device name and file 
system label which is completely broken on SATA systems which do dynamic
assignment.  e2label was a great idea, but did not go far enough to 
abstract. 

The Initial mount sequence using:

 root=LABEL=/

should be modified to ignore the device assignment and dunamically scan 
the drives for the root drive for initial bootup and DETECT
the device assignment rather then reverting to fixed device 
assignments.  As implemented it's pretty useless and is simply an aliasing
mechanism rather than solving the problem of the system being truly 
dynamic. 

On many systems, including the systems we ship, /dev/sda, /dev/sdb, and 
/dev/sdc are dynamically created from 3Ware RAID arrays and the boot drive
on the SATA connectors of the motherboard tends to "float" (i.e. sdc can 
move to sda or sdb between boots depending on how the arrays are 
configured).
On a RAID 0 failure, by way of example, sdc becomes sdb and renders a 
system unable to boot.  The solution is to setup the initial scanning 
for root to look for the "/" assignment from e2label, and dynamically 
assign the /dev/sdX handle from this scanning. 

Just a suggestion.

Jeff



             reply	other threads:[~2006-03-28 20:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 21:48 Jeff V. Merkey [this message]
2006-03-28 23:29 ` e2label suggestions Theodore Ts'o
2006-03-29  0:25   ` Jeff V. Merkey
2006-03-29  0:13     ` Jeff Garzik
2006-03-29  1:18       ` Jeff V. Merkey
2006-03-29  1:40         ` Theodore Ts'o
2006-03-29  2:34           ` Jeff V. Merkey
2006-03-29 19:32             ` Bill Davidsen

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=4429AF42.1090101@soleranetworks.com \
    --to=jmerkey@soleranetworks.com \
    --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