touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #63850
[Bug 995645] Re: udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y''
*** This bug is a duplicate of bug 1396213 ***
https://bugs.launchpad.net/bugs/1396213
** This bug has been marked a duplicate of bug 1396213
LVM VG is not activated during system boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/995645
Title:
udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm
vgchange -a y''
Status in lvm2 package in Ubuntu:
Confirmed
Bug description:
Boot takes a long time during which the console reports:
[ 100.224928] device-mapper: table: 252:40: snapshot: Snapshot cow pairing for exception table handover failed
udevd[617]: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'' [1148]
udevd[617]: 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a
y'' [1148] terminated by signal 9 (Killed)
Then the boot stalls waiting to mount /usr and I have to use M to
manually recover.
When I get into the recovery shell, a read from
/dev/rootvol_tmp/ubuntu_usr returns 0 bytes and I have to run
"vgchange -a y" before I can get a read from that LV to return data.
At that point I can drop out of the recovery shell and boot will
continue.
I have the following LVs on this system:
# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
video datavol -wn-ao 698.19g
video_tmp datavol -wi-a- 233.32g
apt_archives rootvol_tmp -wi-a- 1.00g
home rootvol_tmp -wi-ao 1.78g
lucid rootvol_tmp -wi-a- 3.00g
lucid_root rootvol_tmp swi-a- 1.00g ubuntu_root 34.70
lucid_usr rootvol_tmp swi-a- 5.00g ubuntu_usr 42.22
lucid_var rootvol_tmp swi-a- 4.00g ubuntu_var 39.57
myth-0.24_root rootvol_tmp swi-a- 1.00g ubuntu_root 34.66
myth-0.24_usr rootvol_tmp swi-a- 5.00g ubuntu_usr 35.68
natty_root rootvol_tmp swi-a- 500.00m ubuntu_root 49.99
natty_usr rootvol_tmp swi-a- 2.49g ubuntu_usr 58.34
swap rootvol_tmp -wi-ao 512.00m
ubuntu_root rootvol_tmp owi-ao 500.00m
ubuntu_root-20111213 rootvol_tmp swi-a- 500.00m ubuntu_root 70.96
ubuntu_root-20120209 rootvol_tmp swi-a- 500.00m ubuntu_root 70.95
ubuntu_root-20120214 rootvol_tmp swi-a- 500.00m ubuntu_root 70.94
ubuntu_root-20120220 rootvol_tmp swi-a- 500.00m ubuntu_root 70.93
ubuntu_root-20120313 rootvol_tmp swi-a- 500.00m ubuntu_root 70.93
ubuntu_root-20120319 rootvol_tmp swi-a- 500.00m ubuntu_root 70.90
ubuntu_root-20120412 rootvol_tmp swi-a- 500.00m ubuntu_root 50.03
ubuntu_usr rootvol_tmp owi-ao 2.49g
ubuntu_usr-20111213 rootvol_tmp swi-a- 2.49g ubuntu_usr 69.04
ubuntu_usr-20120209 rootvol_tmp swi-a- 2.49g ubuntu_usr 68.64
ubuntu_usr-20120214 rootvol_tmp swi-a- 2.49g ubuntu_usr 67.79
ubuntu_usr-20120220 rootvol_tmp swi-a- 2.49g ubuntu_usr 67.52
ubuntu_usr-20120313 rootvol_tmp swi-a- 2.49g ubuntu_usr 67.41
ubuntu_usr-20120319 rootvol_tmp swi-a- 2.49g ubuntu_usr 66.21
ubuntu_usr-20120412 rootvol_tmp swi-a- 2.49g ubuntu_usr 65.69
ubuntu_var rootvol_tmp owi-ao 1.99g
That's probably more than most people, but certainly not enough to
warrant an unbootable system I should not think.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: udev 175-0ubuntu9
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
CurrentDmesg:
[ 237.755758] NFSD: starting 90-second grace period
[ 256.877022] SysRq : Changing Loglevel
[ 256.880020] Loglevel set to 8
CustomUdevRuleFiles: 85-alsa.rules 85-ifupdown.rules 85-mdadm.rules 41-mythtv-permissions.rules
Date: Sun May 6 17:02:19 2012
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic root=/dev/mapper/rootvol_tmp-ubuntu_root ro console=ttyS0,115200 console=tty0 resume=/dev/mapper/rootvol-swap crashkernel=384M-2G:64M,2G-:128M vmalloc=256M
SourcePackage: udev
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/26/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080009
dmi.board.name: P4P800SE
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 2.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080009:bd03/26/2004:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4P800SE:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/995645/+subscriptions