Red Hat Bugzilla – Bug 244202
Boot fails if any LVM snapshots are full
Last modified: 2013-09-02 02:20:44 EDT
Description of problem:
When booting off LVM, the initrd tries to activate all LVs. This fails if there
are any full snapshots, and initrd fails to recover from the error, leading to a
failure to boot.
Version-Release number of selected component (if applicable):
100%, I believe.
Steps to Reproduce:
1. Create a small snapshot of the root filesystem ("lvcreate -s ...")
2. Write enough data to the root filesystem to overflow the snapshot ("lvs" will
show it at 100% full)
Boot fails with a nash SEGV
Boot log from the boot failure:
device-mapper: ioctl: 4.11.0-ioctl (2006-09-14) initialised: firstname.lastname@example.org
Reading all physical volumes. This may take a while...
Found volume group "spectre" using metadata type lvm2
device-mapper: snapshots: snapshot is marked invalid
device-mapper: table: 253:3: snapshot: Failed to read snapshot metadata
device-mapper: ioctl: error adding target to table
device-mapper: reload ioctl failed: Invalid argument
10 logical volume(s) in volume group "spectre" now active
nash received SIGSEGV! Backtrace:
Kernel panic - not syncing: Attempted to kill init!
Fortunately, a readonly rescue boot off CD _does_ boot successfully, and the
situation can then be recovered by removing the full snapshot volume.
Created attachment 157009 [details]
this is a fix.
Fix is attached. Proposing for 5.2 .
Related to bug 244215 - activation of snapshot marked invalid.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Fixed in mkinitrd-220.127.116.11-20 .
Unable to reproduce on 5.1, however 5.0 appears to consistently trigger the failure.
With the help of Stephen, created a 5.0 and 5.2 (snap#5 20080409) install with a
full lvm snapshot, as seen below:
LV VG Attr LSize Origin Snap% Move Log Copy%
root VolGroup00 owi-ao 3.91G
snap1 VolGroup00 Swi-I- 32.00M root 100.00
swap VolGroup00 -wi-ao 1.94G
* The i386+x86_64+ppc+s390x 5.0 systems nash segfault on reboot as noted in
* The i386+x86_64+ppc+s390x 5.2 systems do not segfault upon reboot.
Moving to VERIFIED
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.