From: lvm@interlinx.bc.ca
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] file system larger than lv
Date: Fri Nov 15 06:28:02 2002 [thread overview]
Message-ID: <20021115122708.GK8377@pc.ilinx> (raw)
In-Reply-To: <20021115115831.B11618@sistina.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Fri, Nov 15, 2002 at 11:58:31AM +0100, Heinz J . Mauelshagen wrote:
>
Heinz,
> LVM1 contains the e2fsadm tool which prevents
> you form doing things like that.
I know we are never going to be able to stop everybody who _really_
wants to shoot themselves in the foot from doing so, but I wonder,
perhaps if there should be "something extra" that needs to be done to
manipulate the size of volumes with filesystems on them (i.e. probe
the lv to see what's on it) directly (i.e. lvreduce, lvexpand). This
would of course be used to encourage the use of the convenience tools
like e2fsadm.
Perhaps an environment variable or an "expert switch" on the command
line or something. Not using the switch or setting the env. variable
would cause a probe of the lv and if there was found to be a
filesystem on it, it would prompt the user to use a convenience tool
(for that filesystem type) to perform his task, or set the
switch/variable, if he really wanted to go ahead.
Or maybe this is all just too much handholding.
b.
--
Brian J. Murrell
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-11-15 6:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 9:36 [linux-lvm] file system larger than lv Jonathan S. Polacheck
2002-11-15 5:04 ` Heinz J . Mauelshagen
2002-11-15 6:28 ` lvm [this message]
2002-11-15 7:00 ` Heinz J . Mauelshagen
2002-11-15 7:50 ` lvm
2002-11-15 20:00 ` Ragnar Kjørstad
2002-11-18 9:30 ` Heinz J . Mauelshagen
2002-11-18 9:32 ` Heinz J . Mauelshagen
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=20021115122708.GK8377@pc.ilinx \
--to=lvm@interlinx.bc.ca \
--cc=linux-lvm@sistina.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.