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: Mon Nov 18 09:32:02 2002	[thread overview]
Message-ID: <20021118162556.C25728@sistina.com> (raw)
In-Reply-To: <20021115134816.GL8377@pc.ilinx>; from lvm@interlinx.bc.ca on Fri, Nov 15, 2002 at 08:48:20AM -0500

On Fri, Nov 15, 2002 at 08:48:20AM -0500, lvm@interlinx.bc.ca wrote:
> On Fri, Nov 15, 2002 at 01:54:24PM +0100, Heinz J . Mauelshagen wrote:
> > 
> > Brian,
> 
> Hi Heinz.
> 
> > 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 ;)
> 
> I hear ya.  Me too.  :-)

:)

> 
> > 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.
> 
> I don't disagree with that.
> 
> > Putting additional overloading block/filesystem layer services not necessarily
> > needed there into the kernel is unlikely to be accepted either IMO.
> 
> No.  No.  Not in the kernel.  I mean the user space tools can simply
> check what data is on the block device (i.e. look for a known
> signature of given filesystems) and see if it can determine if it is
> indeed a filesystem.

Yep. We share the same opinion I guess.
The user space tool shall be pattern configurable in order to "learn" about
new filesystem types (config file ala /etc/magic).

> 
> > 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.
> 
> That is fair enough.  And I don't care that strongly about this issue,
> but just thought of how many tools (in their "interactive mode"
> anyway) stop and ask a user before they are about to do something
> potentially disasterous.

lvreduce warns.
As mkfs does ;)

> 
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      parent reply	other threads:[~2002-11-18  9:32 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
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 [this message]

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=20021118162556.C25728@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.