From: Heinz Mauelshagen <mauelsha@ez-darmstadt.telekom.de>
To: rjakob@duffy1.franken.de
Cc: mge@ts1.ez-darmstadt.telekom.de, linux-lvm@msede.com
Subject: Re: [linux-lvm] lvm-0.6, Linux 2.2.9 and devfs-patch-v99.2
Date: Mon, 21 Jun 1999 1:41:37 METDST [thread overview]
Message-ID: <199906202342.AA11684@mailgate1b.telekom.de> (raw)
In-Reply-To: <m10vk14-0000YbC@duffy1.franken.de>; from "Rolf Jakob" at Jun 20, 99 6:00 pm
>
> > What about:
> >
> > http://www.dsv.nl/~buytenh/ext2resize/
> >
> > i've no idea whether it works or not.
>
Thanks Rolf for finding ext2resize 8*)
> It works - hmm, sometimes :-)
At here maybe 8*)
The author's example works.
Tried to extend a filesytem of 200M to 252M --> SEGFAULT --> 8*(
Extending from 200M to 204M --> SEGFAULT too.
Have to dig deaper into the code...
> I managed to resize a mounted file system and several times it was possible
> to copy more files on it after the resize. But from time to time I got an
> error saying "no space left on device" while df shows the free space
> correctly.
ext2 is not implemented with filesystem locking which is necessary
for mounted resizes. The resizer changes the on disk structs.
What you see should basically depend on what is in the cache and what isn't.
Another issue is, that ext2 Block Descriptor Tables don't have to
be changed in size, if extensions or reductions are small.
Your experience with "no space left on device" could by accident
correlate to these facts.
> Just some minutes ago I sent some feedback to the author (of course
> mentioning lvm :-) and a patch (the snapshot of June, 17th would not get
> the size of a block device).
It has to ensure, that the filesystem is not mounted as well!
> It looks very promising.
Yep.
Heinz
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Systemmanagement C/S Deutsche Telekom AG
Entwicklungszentrum Darmstadt
Heinz Mauelshagen Otto-Roehm-Strasse 71c
Senior Systems Engineer Postfach 10 05 41
64205 Darmstadt
mge@ez-darmstadt.telekom.de Germany
+49 6151 886-425
FAX-386
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~1999-06-20 23:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-18 0:15 [linux-lvm] lvm-0.6, Linux 2.2.9 and devfs-patch-v99.2 Rolf Jakob
1999-06-18 6:56 ` Heinz Mauelshagen
1999-06-18 18:15 ` Jens-Uwe Mager
1999-06-18 20:41 ` Michael Loftis
1999-06-18 18:59 ` Rolf Jakob
1999-06-20 9:03 ` Rainer Clasen
1999-06-20 11:28 ` Paul Jakma
1999-06-20 16:00 ` Rolf Jakob
1999-06-20 22:37 ` Stefan Monnier
1999-06-20 23:36 ` Rolf Jakob
1999-06-20 23:41 ` Heinz Mauelshagen [this message]
1999-06-20 23:47 ` Paul Jakma
-- strict thread matches above, loose matches on Subject: below --
1999-06-12 17:51 Rolf Jakob
1999-06-13 22:30 ` Heinz Mauelshagen
1999-06-14 22:01 ` Rolf Jakob
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=199906202342.AA11684@mailgate1b.telekom.de \
--to=mauelsha@ez-darmstadt.telekom.de \
--cc=linux-lvm@msede.com \
--cc=mge@ts1.ez-darmstadt.telekom.de \
--cc=rjakob@duffy1.franken.de \
/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.