From: Jan Niehusmann <jan@gondor.com>
To: benr@us.ibm.com
Cc: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>, linux-lvm@msede.com
Subject: Re: [linux-lvm] Re: IBM to release LVM Technology to the Linux
Date: Fri, 30 Jun 2000 11:34:18 +0200 [thread overview]
Message-ID: <20000630113418.A8639@gondor.com> (raw)
In-Reply-To: <8525690D.0082015B.00@d54mta02.raleigh.ibm.com>; from benr@us.ibm.com on Thu, Jun 29, 2000 at 06:39:51PM -0500
On Thu, Jun 29, 2000 at 06:39:51PM -0500, benr@us.ibm.com wrote:
> 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.
We'll always have that kind of 'data security hole'. We have lvreduce, we
have mke2fs, we even have cat /dev/zero >/dev/hda.
I think admin tools should be easily usable, and that includes safety. It
should be difficult to destroy data accidently. So, obviously, it's a bad
thing if you have to shrink the fs size first, then shrink the volume size,
and if you misstype one of the sizes you lose data.
I see two possible solutions: One is an integrated tool like e2fsadm,
generalized to know about all possible filesystems. (If you call it to
shrink a fs that it doesn't know about, it fails with a proper error
message).
The second is a check in lvreduce to ensure the fs on the partition fits into
the new volume size. The user still has to call ext2resize (or another tool)
first, and then lvreduce, but user faults are caught.
(Of course, lvreduce will have a --i-know-this-doesnt-fit-do-it-anyway option
to allow the admin to shoot himself in the foot if he really wants to...)
I know the proposed LVMS does much more than providing data security, but I'm
just not interested in many of the features, so I don't comment on them. What
I like about LVM (and I think I share this opinion with many other people) is
the ability to change partition sizes without big data moving tasks, and
without the need to care about drive borders.
And I know about the dangers of lvreduce, it did already bite me once. :-)
Jan
next prev parent reply other threads:[~2000-06-30 9:34 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
2000-06-30 9:34 ` Jan Niehusmann [this message]
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=20000630113418.A8639@gondor.com \
--to=jan@gondor.com \
--cc=benr@us.ibm.com \
--cc=linux-lvm@msede.com \
--cc=lvm@ragnark.vestdata.no \
/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.