On Mon, 2009-02-23 at 17:44 +0000, Alasdair G. Kergon wrote:
> It's also worth trying it without any vgscans at all - it ought to
> cope without nowadays provided all commands access VGs by name
> i.e. 'vgchange -ay vg1' and never 'vgchange -ay'.
> It'll trigger a vgscan internally if it can't find a VG that
> was explicitly named.
>
Which will cause the exact same problem we're seeing :-/
Scott
--
Scott James Remnant
<email address hidden>
On Mon, 2009-02-23 at 17:44 +0000, Alasdair G. Kergon wrote:
> It's also worth trying it without any vgscans at all - it ought to
> cope without nowadays provided all commands access VGs by name
> i.e. 'vgchange -ay vg1' and never 'vgchange -ay'.
> It'll trigger a vgscan internally if it can't find a VG that
> was explicitly named.
>
Which will cause the exact same problem we're seeing :-/
Scott
--
Scott James Remnant
<email address hidden>