Linux LVM users
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm 1 unable to boot
Date: Thu, 1 Apr 2004 15:48:33 +0200	[thread overview]
Message-ID: <20040401134833.GG29222@redhat.com> (raw)
In-Reply-To: <1080765764.12286.20.camel@lupin.private.cimr.cam.ac.uk>

On Wed, Mar 31, 2004 at 09:42:44PM +0100, Geoff Dolman wrote:
> On Wed, 2004-03-31 at 16:49, Patrick Caulfield wrote:
> > On Wed, Mar 31, 2004 at 03:59:39PM +0100, Geoff Dolman wrote:
> > > Hi
> > > 
> > > I have a machine with the following partition structure:
> > > 
> > > /dev/sda1 /boot (ext3)
> > > /dev/sda2 swap
> > > /dev/sda3 LVM
> > > 
> > > The LVM (1.03/rh9) contains one PV and this has Volume00 in it which
> > > contains lvs for slash, usr, var, /usr/local and so on...
> > > 
> > > I rebooted the machine for the first time in ages (same kernel
> > > configuration as the last reboot and no changes - or very few).
> > > 
> > > The machine won't reboot - it panics because of a message (something)
> > > like:
> > > 
> > > vgscan found inactive "Volume00"
> > > Error 28 Unable to make /etc/lvmtab.d/Volume00/Volume00.tmp
> > > vg_cfgbackup.c line 273
> > > 
> > 
> > Error 28 is ENOSPC - your initrd is too small to hold the metadata backups.
> 
> Thanks - but how do I fix this?

Append the kernel boot parameter "ramdisk_size=" and give a size in kilobytes
(eg, 'ramdisk_size=16384' makes 16MB ram disks.

> 
> cheers
> 
> Geoff
> 
> -- 
> JDRF/WT Diabetes and Inflammation Laboratory
> Cambridge Institute for Medical Research
> University of Cambridge
> http://www-gene.cimr.cam.ac.uk/todd/
> 
> _______________________________________________
> 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/

-- 

Regards,
Heinz    -- The LVM Guy --

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

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

Heinz Mauelshagen                                 Red Hat GmbH
Consulting Development Engineer                   Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  parent reply	other threads:[~2004-04-01 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31 14:59 [linux-lvm] lvm 1 unable to boot Geoff Dolman
2004-03-31 15:49 ` Patrick Caulfield
2004-03-31 19:33   ` [linux-lvm] max LV size Alexander Lazarevich
2004-04-01 13:44     ` Heinz Mauelshagen
2004-03-31 20:42   ` [linux-lvm] lvm 1 unable to boot Geoff Dolman
2004-03-31 20:10     ` Martijn Schoemaker
2004-03-31 20:58     ` Re : " Jean-Luc Coulon (f5ibh)
2004-04-01 13:48     ` Heinz Mauelshagen [this message]
2004-04-01 14:49       ` Jean-Luc Coulon (f5ibh)
2004-04-01 14:54         ` 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=20040401134833.GG29222@redhat.com \
    --to=mauelshagen@redhat.com \
    --cc=linux-lvm@redhat.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