linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Michael Marxmeier <mike@msede.com>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] Problems with e2fsadm
Date: Fri, 8 Oct 99 0:42:55 MESZ	[thread overview]
Message-ID: <199910072242.AAA18522@e35.msede.com> (raw)
In-Reply-To: <m11ZHs9-000D4UC@londo.rhein-main.de>; from "Torsten Neumann" at Oct 7, 99 8:02 pm

> 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/

      parent reply	other threads:[~2020-11-27 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

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=199910072242.AAA18522@e35.msede.com \
    --to=mike@msede.com \
    --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 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).