From: Igor M Podlesny <for.poige+linux@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
Alasdair G Kergon <agk@redhat.com>
Subject: > You may find that you need to update your lvm userspace tools.
Date: Tue, 05 Feb 2008 12:32:11 +0700 [thread overview]
Message-ID: <47A7F4DB.3070406@gmail.com> (raw)
In-Reply-To: <20080204052709.12f4e0d3.akpm@linux-foundation.org>
On 2008-02-04 20:27, Andrew Morton wrote:
> On Mon, 04 Feb 2008 20:16:48 +0700 Igor M Podlesny <for.poige+linux@gmail.com> 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?
next prev parent reply other threads:[~2008-02-05 5:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43d009740802022335y21c3f93ep4e444bef71338045@mail.gmail.com>
[not found] ` <20080202235103.20dd9768.akpm@linux-foundation.org>
2008-02-04 13:16 ` Both 2.6.24-mm1 and 2.6.24-git11 do NOT "see" any of mine LVM-2 disks Igor M Podlesny
2008-02-04 13:27 ` Andrew Morton
2008-02-04 13:27 ` Andrew Morton
2008-02-05 5:32 ` Igor M Podlesny [this message]
2008-02-05 5:53 ` > You may find that you need to update your lvm userspace tools Andrew Morton
2008-02-05 5:53 ` Andrew Morton
2008-02-05 12:11 ` Alasdair G Kergon
2008-02-05 12:11 ` Alasdair G Kergon
2008-02-05 6:28 ` NVIDIA's Linux x86 Display Driver fresh driver isn't compatible anymore Igor M Podlesny
2008-02-05 6:34 ` Arjan van de Ven
2008-02-05 6:44 ` > best asked at one of the nvidia forums, not on lkml Igor M Podlesny
2008-02-05 6:53 ` Zachary Amsden
2008-02-05 6:56 ` > global_flush_tlb() would be the correct one Igor M Podlesny
2008-02-05 7:22 ` > best asked at one of the nvidia forums, not on lkml Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47A7F4DB.3070406@gmail.com \
--to=for.poige+linux@gmail.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.