Re: LVM Problems :)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

---

Hi there!

Big thanks for the very fast answer!!
Much appreciated!

Just to be VERY sure, tune2fs -l says:

tune2fs -l /dev/share/data
tune2fs 1.32 (09-Nov-2002)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          e89bf0d8-31fc-4ef0-945a-8cc4bb0c1d4c
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      filetype sparse_super large_file
Default mount options:    (none)
Filesystem state:         not clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              125288448
Block count:              250576896
Reserved block count:     0
Free blocks:              8128738
Free inodes:              125210458
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16384
Inode blocks per group:   512
Filesystem created:       Fri May 30 17:14:27 2003
Last mount time:          Fri Feb 13 14:58:30 2004
Last write time:          Fri Feb 13 14:58:30 2004
Mount count:              12
Maximum mount count:      20
Last checked:             Thu Feb 12 18:53:36 2004
Check interval:           15552000 (6 months)
Next check after:         Tue Aug 10 19:53:36 2004
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128

----

So What lvreduce size should i use to shrink it?
I better have a guru look over it, better safe than
sorry

-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
>
>
>
> *** 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
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> _______________________________________________
> 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

Attachment: pgp00554.pgp
Description: PGP signature


[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux