From: Steve Cousins <steve.cousins@maine.edu>
To: Arne Jansen <sensille@gmx.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid on USB flash disk
Date: Sat, 10 Feb 2007 13:57:51 -0500 [thread overview]
Message-ID: <45CE15AF.5454B3A4@maine.edu> (raw)
In-Reply-To: 45CE0DD9.4050009@gmx.net
Arne Jansen wrote:
>
> The main reason why I'm trying this weird setup is that the USB
> drive is always enumerated last in my kernel, and I want to boot
> from it. That means every time I add a disk or remove one I have
> to edit grub.conf and fstab. Very inconvenient. So my idea was
> to create a single device md on it and leave it to the autodetection
> to find the device. So I never have to edit /etc/fstab again for
> a simple hardware change and I'm independent of any enumeration
> changes in future kernel releases.
>
> But unfortunately it doesn't work :-(
Sorry not to answer your main question but why not use labels in your
USB device partitions and use the labels in your fstab. This will make
it so it doesn't matter which dev file it uses.
Steve
next prev parent reply other threads:[~2007-02-10 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-10 18:24 Raid on USB flash disk Arne Jansen
2007-02-10 18:57 ` Steve Cousins [this message]
2007-03-05 16:38 ` Rob Bray
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=45CE15AF.5454B3A4@maine.edu \
--to=steve.cousins@maine.edu \
--cc=linux-raid@vger.kernel.org \
--cc=sensille@gmx.net \
/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).