From: Wolfgang Weisselberg <weissel@netcologne.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Backup costs (was: LVM reimplementationre)
Date: Thu Feb 7 17:05:02 2002 [thread overview]
Message-ID: <20020207225807.GA24019@tiger.bigcats.invalid> (raw)
In-Reply-To: <Pine.LNX.4.10.10202071056180.8754-100000@pzat.meep.org>
Hi, James!
James Hawtin (oolon@ankh.org) wrote 45 lines:
> The reasons resize scares me, is all in needs is someone to define MB or
> GB differently and your up S..T creek, is the block could 1k or 512
> bytes... Was that M option MiB or MB most people say MB whent hey mean
> MiB. Was there and "overhead" of a few blocks magically required when i
> asked for a 1GiB filesystem... etc.
If you are using ext2 or ext3, you might want to look at
e2fsadm...
-Wolfgang
next prev parent reply other threads:[~2002-02-07 17:05 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 13:54 [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementation ready for beta testing Steve Pratt
2002-01-31 14:05 ` [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementationre ady " Jeff Layton
2002-02-01 3:29 ` Heinz J . Mauelshagen
2002-02-01 9:43 ` Jeff Layton
2002-02-05 8:04 ` James Hawtin
2002-02-05 8:09 ` Patrick Caulfield
2002-02-05 11:13 ` Jesus Manuel NAVARRO LOPEZ
2002-02-05 12:28 ` [linux-lvm] (OT) Backups (was Re: LVM reimplementationre ady for beta testing...) Chad C. Walstrom
2002-02-06 13:13 ` [linux-lvm] Backup costs (was: LVM reimplementationre) Benjamin Scott
2002-02-06 13:39 ` Daniel Whicker
2002-02-06 13:46 ` James Mello
2002-02-06 14:35 ` Anders Widman
2002-02-07 3:01 ` Jesus Manuel NAVARRO LOPEZ
2002-02-07 3:17 ` Petro
2002-02-07 4:34 ` Jesus Manuel NAVARRO LOPEZ
2002-02-07 7:19 ` Petro
2002-02-07 7:54 ` Jesus Manuel NAVARRO LOPEZ
2002-02-07 3:55 ` Dieter Stueken
2002-02-06 13:46 ` Andreas Dilger
2002-02-06 13:48 ` Theo Van Dinter
2002-02-06 15:45 ` Austin Gonyou
2002-02-06 13:51 ` Petro
2002-02-06 13:52 ` Kirby C. Bohling
2002-02-06 13:55 ` Jeff Layton
2002-02-06 14:03 ` James Mello
2002-02-06 20:03 ` Jeff Layton
2002-02-06 20:08 ` James Mello
2002-02-06 20:11 ` Jeff Layton
2002-02-07 3:10 ` Jesus Manuel NAVARRO LOPEZ
2002-02-07 4:53 ` Jeff Layton
2002-02-07 5:31 ` James Hawtin
2002-02-07 17:05 ` Wolfgang Weisselberg [this message]
2002-02-08 20:04 ` James Hawtin
2002-02-07 3:03 ` Jesus Manuel NAVARRO LOPEZ
2002-02-07 3:17 ` Petro
2002-02-07 4:15 ` Jesus Manuel NAVARRO LOPEZ
2002-02-12 1:00 ` Marc MERLIN
2002-01-31 15:19 ` [Evms-devel] Re: [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementation ready for beta testing Andrew Clausen
2002-02-01 3:47 ` Joe Thornber
2002-02-01 3:55 ` [Evms-devel] " Arjan van de Ven
2002-02-01 4:04 ` Joe Thornber
2002-02-01 4:13 ` [linux-lvm] " Arjan van de Ven
2002-02-01 4:31 ` Joe Thornber
2002-02-01 5:06 ` [linux-lvm] Re: [Evms-devel] " Stephen C. Tweedie
2002-02-01 8:32 ` [linux-lvm] " Alan Cox
2002-02-01 8:59 ` [linux-lvm] Re: [Evms-devel] " Stephen C. Tweedie
2002-02-01 16:01 ` [evms-devel] [linux-lvm] " Kevin Corry
2002-02-01 17:17 ` Alan Cox
2002-02-02 7:40 ` Andrew Clausen
2002-02-02 13:30 ` Alan Cox
2002-02-03 6:22 ` Joe Thornber
-- strict thread matches above, loose matches on Subject: below --
2002-02-06 21:10 [linux-lvm] Backup costs (was: LVM reimplementationre) Richard Barbara
2002-02-07 10:24 ` Scott Laird
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=20020207225807.GA24019@tiger.bigcats.invalid \
--to=weissel@netcologne.de \
--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