[linux-lvm] ext3 slash

Heinz J . Mauelshagen mauelshagen at sistina.com
Fri Jun 6 05:50:01 UTC 2003


On Fri, Jun 06, 2003 at 11:35:24AM +0100, Geoff Dolman wrote:
> On Fri, 2003-06-06 at 11:05, Geoff Dolman wrote:
> > On Fri, 2003-06-06 at 09:46, Heinz J . Mauelshagen wrote:
> > > On Fri, Jun 06, 2003 at 09:34:37AM +0100, Geoff Dolman wrote:
> > > > Hi
> > > > 
> > > > I have installed a machine with a /boot in a normal partition and all
> > > > other partitions including / on ext3 logical volumes.
> > > > (Red Hat 9/lvm 1.0.3).
> > > > 
> > > > I want to snapshot dump these partitions but I didn't realise at the
> > > > time of the install that I would have to patch the kernel to be able to
> > > > do this with ext3 filing systems.
> > > > I don't want to have to do this so I migrated the partitions to ext2
> > > > using tune2fs and changed fstab.
> > > > 
> > > > In the case of / and /var I booted into rescue mode from cd to run
> > > > tune2fs against those volumes read-only.
> > > > 
> > > > When I rebooted the machine I got a panic because there was no journal
> > > > found on /. Rebooting into rescue mode and restoring the journal on
> > > > slash cures this problem.
> > > > 
> > > > How can I change the slash volume from ext3 to ext2? As I mentioned I
> > > > edited fstab so there must be some other record somewhere telling the
> > > > kernel that slash is ext3 but what? Do I need to make a new initrd.img?
> > > 
> > > Check if your lilo/grub entry contains a "rootfstype=" entry and change that
> > > if it says ext3.
> > > 
> > 
> > 
> > No - unfortunately not - all I have is
> > 
> > title Red Hat Linux (2.4.20-18.9smp)
> >         root (hd0,0)
> >         kernel /vmlinuz-2.4.20-18.9smp ro root=/dev/Volume00/slash
> >         initrd /initrd-2.4.20-18.9smp.img
> > 
> > and a similar entry for UP.
> 
> More Information:
> 
> On a test machine I have just booted from cd into rescue mode and tried
> to use lvmcreate_initrd.img to make a new initrd.img after changing / to
> ext2.
> I got cpio not enough space on device as an error message even though
> the machine is nowhere near full on any filesystem including /tmp.
> 
> I then tried using mkinitrd to do the same thing and edited grub and
> rebooted. This has worked with the minor inconvenience of having to do
> an fsck when the machine rebooted.

Hmmm, didn't expect an /etc/fstab (which will have an fs type filed entry)
in the initrd.

> 
> -- 
> Geoff Dolman <geoff.dolman at cimr.cam.ac.uk>
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm at sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen at Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-




More information about the linux-lvm mailing list