From: Jeff Garzik <jgarzik@pobox.com>
To: Thomas Horsten <thomas@horsten.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: ATARAID userspace configuration tool
Date: Tue, 10 Feb 2004 13:44:41 -0500 [thread overview]
Message-ID: <40292699.7070200@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0402101743020.28534-100000@jehova.dsm.dk>
Thomas Horsten wrote:
> That's true of course, one example would be to remove the RAID superblock
> with dd. The problem is if this is done by mistake, it could be
> catastrophic. It might be enough to remove the wrong partitions (with
> BLKPG_DEL_PARTITION, thanks to Matt Domsch for pointing me in the right
> direction), it will at least prevent mkfs /dev/hda1 etc, which would have
> unforeseeable consequences.
There are 1001 things that could have unforseen consequences, when root
is doing something ;-)
This is getting into the area of standard Linux kernel policy (or lack
thereof): let root shoot himself in the foot, if he wishes.
I would certainly -want- to be able to dd -from- my underlying disks,
even if an ataraid or md device is sitting on top, for example.
Jeff
next prev parent reply other threads:[~2004-02-10 18:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 14:18 ATARAID userspace configuration tool Thomas Horsten
2004-02-10 14:18 ` Thomas Horsten
2004-02-10 14:51 ` Matt Domsch
2004-02-10 14:58 ` Christophe Saout
2004-02-10 18:26 ` Kevin P. Fleming
2004-02-10 18:26 ` Kevin P. Fleming
2004-02-10 19:18 ` Christophe Saout
2004-02-10 19:24 ` Kevin P. Fleming
2004-02-10 19:24 ` Kevin P. Fleming
2004-02-11 1:35 ` Greg KH
2004-02-11 1:45 ` Kevin P. Fleming
2004-02-11 1:45 ` Kevin P. Fleming
2004-02-11 11:34 ` Christophe Saout
2004-02-11 14:18 ` Kevin P. Fleming
2004-02-11 14:18 ` Kevin P. Fleming
2004-02-11 19:48 ` Christophe Saout
2004-02-10 17:38 ` Jeff Garzik
2004-02-10 17:47 ` Thomas Horsten
2004-02-10 17:47 ` Thomas Horsten
2004-02-10 18:44 ` Jeff Garzik [this message]
2004-02-10 22:41 ` Neil Brown
2004-02-10 22:41 ` Neil Brown
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=40292699.7070200@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=thomas@horsten.com \
/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.