Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] ext3 slash
Date: Fri Jun  6 05:50:01 2003	[thread overview]
Message-ID: <20030606123747.A26918@sistina.com> (raw)
In-Reply-To: <1054895724.11446.30.camel@lupin>; from geoff.dolman@cimr.cam.ac.uk on Fri, Jun 06, 2003 at 11:35:24AM +0100

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@cimr.cam.ac.uk>
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@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@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-06-06  5:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06  3:35 [linux-lvm] ext3 slash Geoff Dolman
2003-06-06  3:59 ` Heinz J . Mauelshagen
2003-06-06  5:06   ` Geoff Dolman
2003-06-06  5:36     ` Geoff Dolman
2003-06-06  5:50       ` Heinz J . Mauelshagen [this message]
2003-06-07  9:50 ` Luca Berra

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=20030606123747.A26918@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox