Re: lvm bug - possible solution

[Robert van der Meulen <rvdm@cistron.nl>]

Quoting John H. Robinson, IV (jhriv@ucsd.edu):
> what about the unexpected reboot? could that cause all the filesystems
> inside the lvm to become unmountable? (factor filesystem corruption out
> of the question for this scenario - i am interested only in the lvm part
> of the equation)
If you leave 'filesystem corruption' out of the equation, it will give you
the filesystems as they were the last time 'vgscan' ran.

If you run 'vgscan' after each change to an lvm volume (or a couple), to
recreate /etc/lvmtab and /etc/lvmtab.d, it will always be up to date, and
there will be no problem.

This is all 'afaik', i will check this first before i update the lvm
packages.

Greets,
	Robert

-- 
			      Linux Generation
   encrypted mail preferred. finger rvdm@debian.org for my GnuPG/PGP key.
			 <Fluor-> Robert is god...