From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM Problems :)
Date: Sat Feb 14 05:10:01 2004 [thread overview]
Message-ID: <20040214101120.GA22753@redhat.com> (raw)
In-Reply-To: <402D1432.8030003@demonlord.de>
On Fri, Feb 13, 2004 at 07:15:14PM +0100, Christian Reiss wrote:
> Greetings again,
>
> Yes, of course it was not a rogue lvm ;)
> Fun is a must, eh?
:)
>
> Anyway,
> Here is my recipe of shrinking the lvm.
> I hope i got it right, now with the e2fsadm thingy:
If you want to shrink a VG in order to reduce it by PVs, there's
no need to deactivate the VG (see below).
Regards,
Heinz -- The LVM Guy --
>
> 1. unmount it
> 2. e2fsadm -L-(SIZE)G /dev/share/data
> 3. pvmove /dev/(HDD)
Not needed > 4. vgchange -a n
4. vgchange -x y
> 5. vgreduce share /dev/(HDD)
Not needed > 6. vgchange -a y
6. vgchange -x n
> 7. fdisk /dev/(HDD)
> 8. mkfs.ext2 auf /dev/(HDD)
> 9. Copy files to reduce data amount on LVM
> 10. repeat
>
> Or am i missing anything? :)
> If not, i will spent some hours of GREAT FUN
> shrinking it. Ahh, the fsck's, movings and.. :)
>
> -Christian.
> BTW: Awesome support! :)
>
>
>
>
> Heinz Mauelshagen wrote:
> >On Fri, Feb 13, 2004 at 06:06:59PM +0100, Christian Reiss wrote:
> >
> >>Greetings again,
> >>
> >>Curious, I replied, but did not recive a copy of my reply,
> >>maybe it got lost in the internet? :) Killed by a rogue lvm,
> >>I assume ;) - If this was/is only me missing my reply, then
> >>I am deeply sorry for spamming - not intentionally, really.
> >
> >
> >Christian,
> >
> >as long as you agree that it wasn't LVM it is no problem ;-)
> >
> >
> >>---
> >>
> >>Hi there!
> >>
> >>Big thanks for the very fast answer!!
> >>Much appreciated!
> >>
> >>Just to be VERY sure, tune2fs -l says:
> >>
> >
> ><SNIP>
> >
> >>Block count: 250576896
> >
> ><SNIP>
> >
> >>Block size: 4096
> >
> ><SNIP>
> >
> >>So What lvreduce size should i use to shrink it?
> >>I better have a guru look over it, better safe than
> >>sorry
> >
> >
> >250576896 * 4KB / 1024MB/KB= 978816MB (which is a multiple of 32MB)
> >
> >->
> >
> ># lvreduce -L 978816M /dev/share/data
> >
> >That should free 112640MB or 3520 PEs in your VG.
> >
> >
> >BTW: you should either run e2fsadm to grow/shrink the unmounted
> > filesystem _and_ the logical volume in one go
> > -or-
> > use the filesystem resizer and lvextend/lvreduce in the correct order
> > (lvextend + grow fs -or- shrink fs + lvreduce).
> >
> > Problem with the later is getting the size arguments right ;-)
> >
> >
> >Regards,
> >Heinz -- The LVM Guy --
> >
> >
> >
> >
> >>-Christian.
> >>
> >>Heinz Mauelshagen wrote:
> >>
> >>
> >>>Christian,
> >>>
> >>>the size of your filesystem and logical volume differs already.
> >>>That's why e2fsadm fails.
> >>>Did you eventually run resize2fs in order to shrink the filesystem ?
> >>>
> >>>Your logical volume size is 1091456MB (32MB/PE * 34108 PE) but your
> >>>filesystem size is 963584GB (941GB * 1024MB/GB; check with
> >>>"tune2fs -l" and look for the block count and block size to calculate
> >>>this correctly).
> >>>
> >>>In case the result shows, that your filesystem is already smaller
> >>
> >>than the LV,
> >>
> >>>lvreduce the logical volume appropriately.
> >>>
> >>>Use the block count * block size result and round it up to the next PE!
> >>>
> >>>Regards,
> >>>Heinz -- The LVM Guy --
> >>>
> >>>
> >>>
> >>>
> >>>On Fri, Feb 13, 2004 at 03:06:28PM +0100, Christian Reiss wrote:
> >>>
> >>>
> >>>>Greetings!
> >>>>
> >>>>I am trying to dissolve a running LVM, so i am doing
> >>>>the e2fsadm, lvreduce, pvmove thingy. But ever since I
> >>>>removed the first hdd, I am unable to resize the lvm
> >>>>any more. The error can be seen below, with e2fsadm.
> >>>>I also included the vg&lvdisplay commands.
> >>>>
> >>>>I am running the LVM1 sources (non-cvs, approx mid last
> >>>>year), as i am unable to run LVM2 (need to downgrade kernel
> >>>>to 2.4.22 (no patch included in lvm2 for 2.4.23)).
> >>>>Also, I am (too dumb/unable) to locate a e2fsadm alike
> >>>>tool for lvm2, as e2fsadm needs the lvm-tab thingy,
> >>>>which lvm2 no longer provides.
> >>>>
> >>>>Any help is greatly appreciated.
> >>>>
> >>>>-Christian.
> >>>>
> >>>>
> >>>>::::::::::::::::::
> >>>>::: vgdisplay ::::
> >>>>
> >>>>--- Volume group ---
> >>>>VG Name share
> >>>>VG Access read/write
> >>>>VG Status available/NOT resizable
> >>>>VG # 0
> >>>>MAX LV 256
> >>>>Cur LV 1
> >>>>Open LV 1
> >>>>MAX LV Size 2 TB
> >>>>Max PV 256
> >>>>Cur PV 11
> >>>>Act PV 11
> >>>>VG Size 1.12 TB
> >>>>PE Size 32 MB
> >>>>Total PE 36668
> >>>>Alloc PE / Size 34108 / 1.04 TB
> >>>>Free PE / Size 2560 / 80 GB
> >>>>VG UUID PSYbaQ-bl8d-xvHp-6re2-hoKd-9mE5-Wa5Tqz
> >>>>
> >>>>:::::::::::::::
> >>>>:: lvdisplay ::
> >>>>
> >>>>--- Logical volume ---
> >>>>LV Name /dev/share/data
> >>>>VG Name share
> >>>>LV Write Access read/write
> >>>>LV Status available
> >>>>LV # 1
> >>>># open 1
> >>>>LV Size 1.04 TB
> >>>>Current LE 34108
> >>>>Allocated LE 34108
> >>>>Allocation next free
> >>>>Read ahead sectors 1024
> >>>>Block device 58:0
> >>>>
> >>>>:::::::::::::
> >>>>:: e2fsadm ::
> >>>>
> >>>>e2fsadm -L-10G /dev/share/data
> >>>>e2fsadm -- logical volume size for "/dev/share/data" invalid
> >>>>
> >>>>:::::::::::
> >>>>:: df -h ::
> >>>>
> >>>>Filesystem Size Used Avail Use% Mounted on
> >>>>/dev/share/data 941G 910G 32G 97% /share/filebase
> >>>>
> >>>>
> >>>>--
> >>>>Christian Reiss <email@demonlord.de>
> >>>>demonserver.de
> >>>>
> >>>>Key fingerprint = 2999 B7CD A218 06DF D658 5BE3 18B6 B232 02FF 71B2
> >>>>Public Key can be obtained here: http://www.demonlord.de/pgp.txt
> >>>_______________________________________________
> >>>linux-lvm mailing list
> >>>linux-lvm@redhat.com
> >>>https://www.redhat.com/mailman/listinfo/linux-lvm
> >>>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >>--
> >>Christian Reiss <email@demonlord.de>
> >>demonserver.de
> >>
> >>Key fingerprint = 2999 B7CD A218 06DF D658 5BE3 18B6 B232 02FF 71B2
> >>Public Key can be obtained here: http://www.demonlord.de/pgp.txt
> >_______________________________________________
> >linux-lvm mailing list
> >linux-lvm@redhat.com
> >https://www.redhat.com/mailman/listinfo/linux-lvm
> >read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
> --
> Christian Reiss <email@demonlord.de>
> demonserver.de
>
> Key fingerprint = 2999 B7CD A218 06DF D658 5BE3 18B6 B232 02FF 71B2
> Public Key can be obtained here: http://www.demonlord.de/pgp.txt
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Red Hat, Inc.
Consulting Development Engineer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2004-02-14 10:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 9:13 [linux-lvm] LVM Problems :) Christian Reiss
2004-02-13 9:38 ` Heinz Mauelshagen
2004-02-13 12:05 ` Christian Reiss
2004-02-13 12:31 ` Heinz Mauelshagen
2004-02-13 13:13 ` Christian Reiss
2004-02-14 5:10 ` Heinz Mauelshagen [this message]
2004-02-13 16:40 ` Chris Cox
2004-02-13 12:08 ` Christian Reiss
2004-02-13 16:14 ` Ken Fuchs
2004-02-14 5:18 ` Heinz Mauelshagen
2004-02-15 12:59 ` Ken Fuchs
2004-02-16 4:27 ` Heinz Mauelshagen
2004-02-16 18:10 ` Ken Fuchs
2004-02-13 9:47 ` AJ Lewis
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=20040214101120.GA22753@redhat.com \
--to=mauelshagen@redhat.com \
--cc=linux-lvm@redhat.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.