* [linux-lvm] Problems with e2fsadm
@ 1999-10-07 18:02 Torsten Neumann
1999-10-12 20:47 ` Heinz Mauelshagen
2020-11-27 16:16 ` Michael Marxmeier
0 siblings, 2 replies; 3+ messages in thread
From: Torsten Neumann @ 1999-10-07 18:02 UTC (permalink / raw)
To: LVM for Linux
Hi,
I'm having some problems with e2fsadm when using 4096 as blocksize for my
ext2 filesystem. e.g
lvcreate -L 100 -n /dev/vg00/lvoltest vg00
mke2fs -b 4096 /dev/vg00/lvoltest
e2fsadm -L 200 /dev/vg00/lvoltest
gives something like
...
lvextend -- logical volume "/dev/vg00/lvoltest" successfully extended
ext2_resize_fs: your container (i.e. the file or partition the
filesystem) is in is not big enough for a filesystem of
204800 blocks (it's only 51200 blocks)
If using resize2fs instead of ext2resize I got the similiar message
The containing partition (or device) is only 51200 blocks.
You requested a new size of 204800 blocks.
Extending ext2 Filesystems on non logical volumes (/dev/sd...) works fine
even if using 4096 as blocksize.
Looking at the ext2resize code it seems to me that ext2resize is doing the
right thing, therefor my guess is that there is some bug in the lvm code.
Looking at LVM I find in tools/lib/liblvm.h
#define BLOCK_SIZE 1024
but I don't understand if this has something to do with the above problem.
BLOCK_SIZE seems to be used in vg_setup_for_extend to check if there is room
for extending. But I don't see what it has to do with the wrong result of
the llseek call in ext2resize.
Maybe here is someone smarter then me and could tell me what's going wrong.
Would be nice if resizing works for all blocksizes.
Regards,
Torsten
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] Problems with e2fsadm
1999-10-07 18:02 [linux-lvm] Problems with e2fsadm Torsten Neumann
@ 1999-10-12 20:47 ` Heinz Mauelshagen
2020-11-27 16:16 ` Michael Marxmeier
1 sibling, 0 replies; 3+ messages in thread
From: Heinz Mauelshagen @ 1999-10-12 20:47 UTC (permalink / raw)
To: Torsten Neumann; +Cc: mge, linux-lvm
Hello Torsten,
e2fsadm simply is buggy in 0.7 when dealing with ext2 4k block sizes.
This will be fixed in 0.8.
Workaround grow : e2fsck, lvextend, resize2fs
Workaround shrink: e2fsck, resize2fs, lvreduce
Regards,
Heinz
>
> I'm having some problems with e2fsadm when using 4096 as blocksize for my
> ext2 filesystem. e.g
> lvcreate -L 100 -n /dev/vg00/lvoltest vg00
> mke2fs -b 4096 /dev/vg00/lvoltest
> e2fsadm -L 200 /dev/vg00/lvoltest
> gives something like
> ...
> lvextend -- logical volume "/dev/vg00/lvoltest" successfully extended
>
> ext2_resize_fs: your container (i.e. the file or partition the
> filesystem) is in is not big enough for a filesystem of
> 204800 blocks (it's only 51200 blocks)
>
> If using resize2fs instead of ext2resize I got the similiar message
>
> The containing partition (or device) is only 51200 blocks.
> You requested a new size of 204800 blocks.
>
> Extending ext2 Filesystems on non logical volumes (/dev/sd...) works fine
> even if using 4096 as blocksize.
> Looking at the ext2resize code it seems to me that ext2resize is doing the
> right thing, therefor my guess is that there is some bug in the lvm code.
> Looking at LVM I find in tools/lib/liblvm.h
> #define BLOCK_SIZE 1024
> but I don't understand if this has something to do with the above problem.
> BLOCK_SIZE seems to be used in vg_setup_for_extend to check if there is room
> for extending. But I don't see what it has to do with the wrong result of
> the llseek call in ext2resize.
>
> Maybe here is someone smarter then me and could tell me what's going wrong.
> Would be nice if resizing works for all blocksizes.
>
> Regards,
> Torsten
>
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Systemmanagement CS-TS T-Nova
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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] Problems with e2fsadm
1999-10-07 18:02 [linux-lvm] Problems with e2fsadm Torsten Neumann
1999-10-12 20:47 ` Heinz Mauelshagen
@ 2020-11-27 16:16 ` Michael Marxmeier
1 sibling, 0 replies; 3+ messages in thread
From: Michael Marxmeier @ 2020-11-27 16:16 UTC (permalink / raw)
To: linux-lvm
> I'm having some problems with e2fsadm when using 4096 as blocksize for my
> ext2 filesystem. e.g
> lvcreate -L 100 -n /dev/vg00/lvoltest vg00
> mke2fs -b 4096 /dev/vg00/lvoltest
> e2fsadm -L 200 /dev/vg00/lvoltest
> gives something like
> ...
> lvextend -- logical volume "/dev/vg00/lvoltest" successfully extended
>
> ext2_resize_fs: your container (i.e. the file or partition the
> filesystem) is in is not big enough for
a filesystem of
> 204800 blocks (it's only 51200 blocks)
This is a bug in e2fsadm which will be fixed with LVM 0.8.
As a workaround you can perform the steps manually.
To extend the file system:
e2fsck - required by resize2fs
lvextend - resize the lvol
resize2fs - resize the fs
To reduce the file system:
e2fsck - required by resize2fs
resize2fs - resize the fs
lvreduce - resize the lvol
Hope this helps
Michael
--
Michael Marxmeier Marxmeier Software AG
E-Mail: mike@msede.com Besenbruchstrasse 9
Phone : +49 202 2431440 42285 Wuppertal, Germany
Fax : +49 202 2431420 http://www.msede.com/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-11-27 16:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-10-07 18:02 [linux-lvm] Problems with e2fsadm Torsten Neumann
1999-10-12 20:47 ` Heinz Mauelshagen
2020-11-27 16:16 ` Michael Marxmeier
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).