From: James Bottomley <James.Bottomley@steeleye.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Kurt Garloff <garloff@suse.de>,
viro@parcelfarce.linux.theplanet.co.uk,
Andrew Morton <akpm@osdl.org>,
hch@infradead.org, SCSI Mailing List <linux-scsi@vger.kernel.org>,
pbadari@us.ibm.com, willy@debian.org
Subject: Re: lots and lots of disks again
Date: 17 Feb 2004 12:57:37 -0500 [thread overview]
Message-ID: <1077040659.2186.31.camel@mulgrave> (raw)
In-Reply-To: <20040217155024.GB4282@pclin040.win.tue.nl>
On Tue, 2004-02-17 at 10:50, Andries Brouwer wrote:
> On Tue, Feb 17, 2004 at 10:18:07AM -0500, James Bottomley wrote:
> > The correct way to solve this is an all or nothing migration gated by a
> > boot time flag.
>
> Yes, I was also thinking of boot time flags, but not all-or-nothing.
> Almost nobody actually needs these five thousand disks, and programs
> like LILO know about major 8, so I can even imagine that someone with
> lots of disks would like the boot disk to remain sda (8,0) even when
> all the others become (1049,*)-(1073,*).
>
> Then what is the boot parameter? I don't know. Anything.
> Say, scsi-legacy=sda,sdb,sde.
But this is complexity for no gain.
The proposal is very simple: You want large numbers or discs or large
numbers of partitions, you get fixed tools and use a flat space on the
new major number. You want legacy, you don't do anything for 2.6; for
2.7 you'll need to specify a boot flag.
James
next prev parent reply other threads:[~2004-02-17 17:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 10:45 lots and lots of disks again Andrew Morton
2004-02-10 11:04 ` Kurt Garloff
2004-02-10 11:26 ` Kurt Garloff
2004-02-10 13:39 ` Christoph Hellwig
2004-02-10 15:47 ` Kurt Garloff
2004-02-10 15:52 ` Christoph Hellwig
2004-02-10 16:08 ` Kurt Garloff
2004-02-10 20:10 ` Andries Brouwer
2004-02-10 20:11 ` Matthew Wilcox
2004-02-10 20:58 ` Kurt Garloff
2004-02-10 21:21 ` viro
2004-02-10 21:34 ` Kurt Garloff
2004-02-10 21:42 ` viro
2004-02-10 22:28 ` Kurt Garloff
2004-02-10 18:26 ` Andrew Morton
2004-02-11 14:56 ` Kurt Garloff
2004-02-11 21:28 ` Andrew Morton
2004-02-11 22:09 ` Kurt Garloff
2004-02-11 22:29 ` Andrew Morton
2004-02-11 22:53 ` viro
2004-02-12 15:00 ` Kurt Garloff
2004-02-12 15:20 ` James Bottomley
2004-02-12 15:57 ` viro
2004-02-12 16:18 ` Kurt Garloff
2004-02-12 16:43 ` James Bottomley
2004-02-16 12:40 ` Kurt Garloff
2004-02-16 22:57 ` Andries Brouwer
2004-02-17 0:56 ` James Bottomley
2004-02-17 7:57 ` Kurt Garloff
2004-02-17 15:08 ` James Bottomley
2004-02-17 15:28 ` Matthew Wilcox
2004-02-17 14:49 ` Andries Brouwer
2004-02-17 15:18 ` James Bottomley
2004-02-17 15:27 ` Kurt Garloff
2004-02-29 16:41 ` James Bottomley
2004-02-29 23:31 ` Kurt Garloff
2004-03-03 19:30 ` Mike Anderson
2004-03-03 19:55 ` Kurt Garloff
2004-02-17 15:50 ` Andries Brouwer
2004-02-17 17:57 ` James Bottomley [this message]
2004-02-17 18:44 ` Andries Brouwer
2004-02-13 0:05 ` Kurt Garloff
2004-02-16 12:31 ` Kurt Garloff
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=1077040659.2186.31.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=aebr@win.tue.nl \
--cc=akpm@osdl.org \
--cc=garloff@suse.de \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=willy@debian.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