All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Niehusmann <jan@gondor.com>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] LVM and I2O
Date: Fri, 8 Sep 2000 09:13:29 +0200	[thread overview]
Message-ID: <20000908091329.A3232@gondor.com> (raw)
In-Reply-To: <20000907224223.B23085@srv.t-online.de>; from Heinz.Mauelshagen@t-online.de on Thu, Sep 07, 2000 at 10:42:23PM +0000

On Thu, Sep 07, 2000 at 10:42:23PM +0000, Heinz J. Mauelshagen wrote:
> On Thu, Sep 07, 2000 at 11:27:59AM -0600, Andreas Dilger wrote:
> > This is "overly safe" and adds complexity to LVM.  There is no such safety
> > check for mkfs or mkswap or fdisk or any number of other ways to destroy
> > your disk...

But mkfs and mkswap are tools that are normally only called manually by an
administrator who should know what he does.

Some lvm tools are called automatically from startup scripts, and if the
partition tables or other config have been changed they may try to access
the wrong partition, so some additional checks may be reasonable.

> If we drop the safety code in the LVM we will still have our officially
> registered 0x8E LVM partiton type identifier which could even be missleading,
> because the partition might be used for different purposes than beeing used
> by LVM.

What about making it a command line option? I can see three possible 
behaviours: 

- no checking of partition types at all
- use /proc/partitions, but do the partition type check wherever possible. 
  If we don't know where the partition table for a given partition is, try
  to use the partition
- require valid partition type, as we currently do. If we don't know how to
  find the partition type, don't use the partition.

I think the second mode could be the default. The first one is not too usefull,
but we may have some kind of --force option that skips the checks, some people
want to be able to shoot themselves in the foot.

Jan

  reply	other threads:[~2000-09-08  7:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-07  3:59 [linux-lvm] LVM and I2O Andreas Dilger
2000-09-07 16:19 ` Heinz J. Mauelshagen
2000-09-07 17:27   ` Andreas Dilger
2000-09-07 22:42     ` Heinz J. Mauelshagen
2000-09-08  7:13       ` Jan Niehusmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-09-08 17:07 Andreas Dilger
2000-09-08 18:28 ` Jan Niehusmann

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=20000908091329.A3232@gondor.com \
    --to=jan@gondor.com \
    --cc=linux-lvm@msede.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.