From: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] file system larger than lv
Date: Fri Nov 15 20:00:02 2002 [thread overview]
Message-ID: <20021116025942.U17827@vestdata.no> (raw)
In-Reply-To: <20021115134816.GL8377@pc.ilinx>; from lvm@interlinx.bc.ca on Fri, Nov 15, 2002 at 08:48:20AM -0500
> > 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.
First of all it's not possible to detect if the device includes a valid
filesystem. You can only check for know filesystems and I don't think it
would be a good idea for lvm to include a list of filesystem-signatures.
Second, reducing the size of a device is just as dangerous if there is
something else (say a datbase) on that device.
So, if anything, I think lvreduce should always warn the user that this
is a dangerous operation.
--
Ragnar Kjørstad
Big Storage
next prev parent reply other threads:[~2002-11-15 20: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
2002-11-15 7:50 ` lvm
2002-11-15 20:00 ` Ragnar Kjørstad [this message]
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=20021116025942.U17827@vestdata.no \
--to=lvm@ragnark.vestdata.no \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox