All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] file system larger than lv
Date: Fri Nov 15 07:00:02 2002	[thread overview]
Message-ID: <20021115135424.A12164@sistina.com> (raw)
In-Reply-To: <20021115122708.GK8377@pc.ilinx>; from lvm@interlinx.bc.ca on Fri, Nov 15, 2002 at 07:27:08AM -0500

Brian,

yes, at the end of the day you can't prevent people with the necessary
credentials from shooting themselves in the foot anyways.
That occasionally includes me.
At least at ~4pm in the morning ;)

Because LVM is a block layer service transparent to filesystems or any other
arbitrary block device user, it should just cover the necessary block device
functionality.

Putting additional overloading block/filesystem layer services not necessarily
needed there into the kernel is unlikely to be accepted either IMO.

Controlling LVM block device and filesystem changes in userspace with an
(e2)fsadm tool is a "helping hand" for the unexperienced, not limiting
the experienced user.
This is our prefered way to go.


On Fri, Nov 15, 2002 at 07:27:08AM -0500, lvm@interlinx.bc.ca wrote:
> 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



-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-11-15  7:00 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
2002-11-15  7:00     ` Heinz J . Mauelshagen [this message]
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=20021115135424.A12164@sistina.com \
    --to=mauelshagen@sistina.com \
    --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.