From: Dale Kemp <dale@inet.net.nz>
To: Linux LVM <linux-lvm@msede.com>
Subject: Re: [linux-lvm] Re: IBM to release LVM Technology to the Linux
Date: Fri, 30 Jun 2000 16:09:55 +1200 [thread overview]
Message-ID: <395C1D93.453EE1A6@inet.net.nz> (raw)
In-Reply-To: 8525690D.0082015B.00@d54mta02.raleigh.ibm.com
>
> "lvreduce allows you to reduce the size of a logical volume. Be careful
> when reducing a logical volume's size, because data in the reduced part is
> lost!!!"
>
> If you are using ext2, then you could use e2fsadm, but if you are using
> another filesystem, then what? Even if you are using ext2, a user could
> still use lvreduce directly. Thus, this is a data security hole.
This is more than a problem with LVM but with device and file system
integration. Even with LVMS the problems not fully solved, maybe only
with JFS but what about ext2, ext3, reiserfs etc. I propose that the list
put some thought into this whole integration process, I think some common
interface standard is needed. Maybe something like the resizefs that I
proposed in a previous email.
toplevel: resizefs <partition_device | logical_volume | mountpoint>
This then calls resizefs.ext2 for example again some thought is needed with
regards to volume's and partition's. Using a common interface now for volumes
could allow the command (or something like it) to work on both LVM and LVMS.
(Maybe also the remount options, etc.)
Its become clear that the most important part is some common elements for
volumes; specifics for each volume manager can be handled in each kernel
module and toolset.
Let's do this now no latter when its all incompatible, for the user's sake.
I say to IBM and SGI please lets get some common functionality, and start
drawing up a proposal document online.
What do you all think?
Proposed common volume management:
- The 'mount' command, and options. Such as readonly etc.
- A resize filesystem command such as "resizefs", that knows about
partitions and
volumes.
- mkfs (eg. mke2fs) should work with all volume types.
- Others to be proposed.
-- Dale.
next prev parent reply other threads:[~2000-06-30 4:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-29 23:39 [linux-lvm] Re: IBM to release LVM Technology to the Linux benr
2000-06-30 4:09 ` Dale Kemp [this message]
2000-06-30 9:34 ` Jan Niehusmann
2000-06-30 15:28 ` Ragnar Kjørstad
-- strict thread matches above, loose matches on Subject: below --
2000-06-30 20:50 benr
2000-06-30 20:28 benr
2000-06-30 20:53 ` Ragnar Kjørstad
2000-06-30 19:27 benr
2000-06-30 21:30 ` Dale Kemp
2000-06-30 23:05 ` Jens Benecke
2000-06-29 5:32 Jean-Eric Cuendet
2000-06-29 10:49 ` Andi Kleen
2000-06-29 1:23 benr
2000-06-29 14:37 ` Ragnar Kjørstad
2000-06-26 21:44 benr
2000-06-27 3:53 ` Paul Jakma
2000-06-26 20:59 benr
2000-06-26 14:27 Wilson, Eric
2000-06-26 23:18 ` Dale Kemp
2000-06-27 2:02 ` Andi Kleen
2000-06-27 2:22 ` Dale Kemp
2000-06-27 2:13 ` Andreas Dilger
2000-06-23 21:04 benr
2000-06-23 23:49 ` Paul Jakma
2000-06-24 6:37 ` Dale Kemp
2000-06-24 18:07 ` S. Ryan Quick
2000-06-25 1:25 ` Dale Kemp
2000-06-26 6:31 ` Martin K. Petersen
2000-06-23 12:52 hpuxadm
2000-06-23 15:20 ` Jens Benecke
2000-06-22 19:37 benr
2000-06-23 1:23 ` Dale Kemp
2000-06-23 20:55 ` Martin K. Petersen
2000-06-21 22:27 benr
[not found] <85256900.007B81E0.00@d54mta02.raleigh.ibm.com>
2000-06-18 22:51 ` Andreas Dilger
2000-06-21 17:28 ` Martin K. Petersen
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=395C1D93.453EE1A6@inet.net.nz \
--to=dale@inet.net.nz \
--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.