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

2008-02-05 Thread Alasdair G Kergon
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

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

2008-02-05 Thread Alasdair G Kergon
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

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

2008-02-04 Thread Andrew Morton
4-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 > userspa

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

2008-02-04 Thread Igor M Podlesny
> > 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

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

2008-02-04 Thread Igor M Podlesny
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

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

2008-02-04 Thread Andrew Morton
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