Re: [ext2resize] Ext2resize for big-endian (Ultrasparc)

[Andreas D. <ad...@tu...>]

Dave Wapstra writes:
> On 21 March, 2001 at 14:14:58 -0700, Andreas Dilger <ad...@tu...> wrote:
> Well, maybe I should say Volume Group instead of filesystem. Here's what I did:
> 
> Created logical volume, made ext2 filesytem, extended logical volume)
> 
> [/root]# pvscan
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE   PV "/dev/sdb" of VG "ftp" [8.43 GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/sdc" of VG "ftp" [8.43 GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/sdd" of VG "ftp" [8.43 GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/sde" of VG "ftp" [8.43 GB / 72 MB free]
> pvscan -- total: 4 [33.74 GB] / in use: 4 [33.74 GB] / in no VG: 0 [0]
> 
> [/root]# ext2resize /dev/ftp/lvol1 33g
> ext2resize v1.1.15 - 2000/08/08 for EXT2FS 0.5b
> ext2resize: ext2_open: invalid superblock
> ext2resize: can't open /dev/ftp/lvol1
> [/root]# pvscan
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE   PV "/dev/sdb"   is associated to an unknown VG (run vgscan)
> pvscan -- ACTIVE   PV "/dev/sdc"   is associated to an unknown VG (run vgscan)
> pvscan -- ACTIVE   PV "/dev/sdd"   is associated to an unknown VG (run vgscan)
> pvscan -- ACTIVE   PV "/dev/sde"   is associated to an unknown VG (run vgscan)
> pvscan -- total: 4 [33.74 GB] / in use: 4 [33.74 GB] / in no VG: 0 [0]
> 
> Note: this output is edited, but does show the problem.  After this, I get 
> 
> vgcreate -- ERROR: VGDA in kernel and lvmtab are NOT consistent; please run vgscan
> 
> and have to do dd if=/dev/zero of=/dev/sd<x> to clear all the tables
> and do a reboot to clean up the VGDA in the kernel

It may very well be that this is an LVM problem.  As you can see, ext2resize
doesn't even succeed in opening the filesystem, so I don't see how it can
corrupt the LVM (actually, it is impossible that writing into /dev/ftp/lvol1
would corrupt LVM metadata (without an LVM bug), because the LVM metadata
is outside the LV itself.

I see you are using Ultrasparc - you need basically todays -ac kernel (or
the Ultrasparc patch from LVM CVS) in order to have LVM work properly on
Ultrasparc.  You also need current CVS LVM kernel patches to have anything
resembling a useful LVM system (I also do a lot of LVM development).  Even
so, I don't think this has seen a lot of testing yet.

Please see if the above (omitted) steps cause LV corruption without any
ext2resize involved.  Please post any findings to the LVM mailing list
lin...@li... (you need to subscribe first).  It would be
useful to see what you have cut out of your process here.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert