To: linux-lvm@redhat.com This is a multi-part message in MIME format. ------=_NextPart_000_0038_01C5D7EC.11C9D1E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, I've used LVM2 in the past, and have followed the steps in the LVM = HOWTO, but have run into problems trying to grow a reiser3 filesystem. = The filesystem has worked fine for several months, but now I'm trying to = make it larger... I've added a pv and am showing free PE's: --- Volume group --- VG Name vg System ID Format lvm2 Metadata Areas 2 Metadata Sequence No 11 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 1 Max PV 0 Cur PV 2 Act PV 2 VG Size 2.44 TB PE Size 4.00 MB Total PE 639113 Alloc PE / Size 320597 / 1.22 TB Free PE / Size 318516 / 1.22 TB VG UUID bADYIh-N4mr-LTJS-5h6b-izph-pgpT-exoOTh ....and I can plug those free PE's into lvextend: lvextend -l+318516 /dev/vg/lv > Extending logical volume lv to 2.44 TB > Logical volume lv successfully resized ....but resize_reiserfs gives errors: resize_reiserfs /dev/vg/lv > resize_reiserfs 3.6.19 (2003 www.namesys.com) > > bread: Cannot read the block (328029183): (Invalid argument). > > reiserfs_open: Your partition is not big enough to contain the > filesystem of (328029183) blocks as was specified in the found = super block. Nothing is written to syslog when resize_reiserfs runs. How can I tell = if this is a LVM2 error providing wrong sizes... or if it's reiserfs = tools having the problems? If I lvreduce things to the initial size I = can remount things OK, and reiserfsck reports no errors. This is an AMD2700+ system running 2.6.13.4, a ReiserFS3 3.6 filesystem = w/ v3.6.19 reiserfsprogs, and LVM2 v2.01.09 utils Any suggestions are appreciated. Thanks! Mike ------=_NextPart_000_0038_01C5D7EC.11C9D1E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi all,

I've used LVM2 in the past, and have = followed the=20 steps in the LVM HOWTO, but have run into problems trying to grow a = reiser3=20 filesystem. The filesystem has worked fine for several months, but now = I'm=20 trying to make it larger...

I've added a pv and am showing free=20 PE's:

    --- Volume = group=20 ---
    VG=20 Name           &nb= sp;  =20 vg
    System ID
    =20 Format           &= nbsp;   =20 lvm2
    Metadata=20 Areas        2
    = =20 Metadata Sequence No 11
    VG=20 Access           &= nbsp;=20 read/write
    VG=20 Status           &= nbsp;=20 resizable
    MAX=20 LV            = ;   =20 0
    Cur=20 LV            = ;   =20 1
    Open=20 LV            = ;  =20 1
    Max=20 PV            = ;   =20 0
    Cur=20 PV            = ;   =20 2
    Act=20 PV            = ;   =20 2
    VG=20 Size           &nb= sp;  =20 2.44 TB
    PE=20 Size           &nb= sp;  =20 4.00 MB
    Total=20 PE            = ; =20 639113
    Alloc PE /=20 Size       320597 / 1.22 = TB
   =20 Free PE / Size       318516 / = 1.22=20 TB
    VG=20 UUID           &nb= sp;  =20 bADYIh-N4mr-LTJS-5h6b-izph-pgpT-exoOTh

....and I can plug those free PE's into = lvextend:

    lvextend -l+318516=20 /dev/vg/lv
    > Extending logical volume lv = to 2.44=20 TB
    > Logical volume lv successfully=20 resized

....but resize_reiserfs gives = errors:

resize_reiserfs=20 /dev/vg/lv
> resize_reiserfs 3.6.19 (2003 www.namesys.com)

> bread: Cannot = read the=20 block (328029183): (Invalid argument).

> reiserfs_open: = Your=20 partition is not big enough to contain the
> = filesystem=20 of (328029183) blocks as was specified in the found super = block.

Nothing is written to syslog when = resize_reiserfs=20 runs. How can I tell if this is a LVM2 error providing wrong sizes... or = if it's=20 reiserfs tools having the problems? If I lvreduce things to the initial = size I=20 can remount things OK, and reiserfsck reports no errors.

This is an AMD2700+ system running = 2.6.13.4, a=20 ReiserFS3 3.6 filesystem w/ v3.6.19 reiserfsprogs, and LVM2 v2.01.09=20 utils

Any suggestions are = appreciated.

Thanks!

Mike

------=_NextPart_000_0038_01C5D7EC.11C9D1E0--