Re: > You may find that you need to update your lvm userspace tools.

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Andrew Morton <akpm@...>
Cc: Igor M Podlesny <for.poige+linux@...>, <linux-kernel@...>, <dm-devel@...>
Date: Tuesday, February 5, 2008 - 8:11 am

On Mon, Feb 04, 2008 at 09:53:04PM -0800, Andrew Morton wrote:

Vague reports like this are sadly a regular occurrence, and they usually
happen when people don't update their initrd after updating their
kernel.  As well as the obvious problems from incompatible modules, some
versions of distros are worse than others, as they foolishly hard-code
device numbers, and a new kernel happens to assign device numbers in a
different sequence breaking everything.  Another cause is when the
distro lets the boot script run too early without waiting for the kernel
to discover all the devices necessary.  Or sometimes kernel/module
changes mean it no longer sees the devices at all.

Alasdair
-- 
agk@redhat.com
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
&gt; global_flush_tlb() would be the correct one., Igor M Podlesny, (Tue Feb 5, 2:56 am)
Re: > You may find that you need to update your lvm users..., Alasdair G Kergon, (Tue Feb 5, 8:11 am)