From: Ulf Bartelt <ulf@twc.de>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] Strange...
Date: Wed, 30 Aug 2000 09:08:38 +0200 [thread overview]
Message-ID: <39ACB2F6.58A01FDA@twc.de> (raw)
In-Reply-To: 20000829195837.A277@guldukat.muon
Hi!
Nils Juergens wrote:
>
> On Tue, 29.08.00, Ulf Bartelt <ulf@twc.de> wrote:
> > (root@kira:/0)~# umount /home/ftp/install/
> > (root@kira:/0)~# umount /home/ftp
> > (root@kira:/0)~# e2fsadm -L+1G /dev/vgkira/ftp
> > e2fsadm -- ERROR: "/dev/vgkira/ftp" is mounted on "/home/ftp2"
> > e2fsadm -- please umount it to resize
> Have you tried using "lvextend" by hand? That should work.
>
> In that case you might try ext2resize instead of resize2fs.
> You don't even need to supply the exact size of the LV to ext2resize.
> "ext2resize <devicename>" will automagically extend the filesystem to
> the size of the LV.
Neither mount nor /proc/mounts claimed the LV to be mounted.
I tried and solved the problem this way:
rename the LV /dev/vgkira/ftp to /dev/vgkira/ptf
(necessary lvchange commands not mentioned)
run e2fsadm on the renamed LV
rename th LV back
use the LV as usual
I had no time to look in the sources but I for now I guess e2fsadm fails
if used on a LV with a name that is the beginning of a LV name that
still is in use...
This was the case having LV names ftp and ftp2...
Bye!
Ulf.
next prev parent reply other threads:[~2000-08-30 7:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-29 7:18 [linux-lvm] Strange Ulf Bartelt
2000-08-29 16:22 ` [linux-lvm] Dazed & Confused Andreas Dilger
2000-08-29 18:32 ` [linux-lvm] rpm Jan Niehusmann
[not found] ` <200009010540.XAA04818@lynx.turbolabs.com>
2000-09-01 11:29 ` [linux-lvm] lvm.h kernel/userspace differences Jan Niehusmann
2000-09-01 11:47 ` [linux-lvm] " Jan Niehusmann
2000-09-01 17:53 ` Andreas Dilger
2000-08-31 18:15 ` [linux-lvm] Dazed & Confused Marcelo Tosatti
2000-09-01 8:01 ` Andreas Dilger
2000-08-29 17:58 ` [linux-lvm] Strange Nils Juergens
2000-08-30 7:08 ` Ulf Bartelt [this message]
2000-09-01 8:25 ` Andreas Dilger
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=39ACB2F6.58A01FDA@twc.de \
--to=ulf@twc.de \
--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 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.