Re: > You may find that you need to update your lvm userspace tools.
On Mon, Feb 04, 2008 at 09:53:04PM -0800, Andrew Morton wrote: > Could someone in dm-devel land please get involved? 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 -- [EMAIL PROTECTED] -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: > You may find that you need to update your lvm userspace tools.
On Tue, 05 Feb 2008 12:32:11 +0700 Igor M Podlesny <[EMAIL PROTECTED]> wrote: > On 2008-02-04 20:27, Andrew Morton wrote: > > On Mon, 04 Feb 2008 20:16:48 +0700 Igor M Podlesny <[EMAIL PROTECTED]> > > wrote: > [...] > >>Now I can say that both 2.6.24-mm1 and 2.6.24-git11 do NOT "see" any > >> of mine LVM-2 disks. pvscan, for e.g., finds nothing at all. > > > > You may find that you need to update your lvm userspace tools. > > You're right; I've updated my initrd with fresh lvm > userspace-counterpart and now the problem has been fixed. Sorry for > groundless alert. > No, breakage of a userspace interface is considered a serious regression. If this was deliberate and utterly unavoidable, well, that's bad but sometimes these things happen. We do prefer to go through elaborate notification processes to minimise the disruption, which afaik did not happen here. If, however, the breakage was was unintentional then we should find the cause and fix it asap, and backport the fix into 2.6.24.1. Please tell us what version of the userspace tools you were previously runnning. Could someone in dm-devel land please get involved? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
> You may find that you need to update your lvm userspace tools.
On 2008-02-04 20:27, Andrew Morton wrote: > On Mon, 04 Feb 2008 20:16:48 +0700 Igor M Podlesny <[EMAIL PROTECTED]> wrote: [...] >>Now I can say that both 2.6.24-mm1 and 2.6.24-git11 do NOT "see" any >> of mine LVM-2 disks. pvscan, for e.g., finds nothing at all. > > You may find that you need to update your lvm userspace tools. You're right; I've updated my initrd with fresh lvm userspace-counterpart and now the problem has been fixed. Sorry for groundless alert. Thanks! -- End of message. Next message? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
