From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <heinrichs@qis-systemhaus.de>
Message-Id: <3B3733F0.94A5F040@qis-systemhaus.de>
Date: Mon, 25 Jun 2001 14:52:00 +0200
From: Dirk Heinrichs <heinrichs@qis-systemhaus.de>
Mime-Version: 1.0
Subject: Re: [linux-lvm] Why vgscan not in kernel?
References: <353310000.993472523@dizzy>
Content-Transfer-Encoding: quoted-printable
Sender: linux-lvm-admin@sistina.com
Errors-To: linux-lvm-admin@sistina.com
Reply-To: linux-lvm@sistina.com
List-Help: <mailto:linux-lvm-request@sistina.com?subject=help>
List-Post: <mailto:linux-lvm@sistina.com>
List-Subscribe: <http://lists.sistina.com/mailman/listinfo/linux-lvm>,
	<mailto:linux-lvm-request@sistina.com?subject=subscribe>
List-Unsubscribe: <http://lists.sistina.com/mailman/listinfo/linux-lvm>,
	<mailto:linux-lvm-request@sistina.com?subject=unsubscribe>
List-Archive: <http://lists.sistina.com/pipermail/linux-lvm/>
List-Id: <linux-lvm.redhat.com>
Content-Type: text/plain; charset="iso-8859-1"
To: linux-lvm@sistina.com

Steven Lembark wrote:
>=20
> >> upon boot, SCSI and IDE drivers check harddrives attached to the device
> >> for partitions. Wouldn't it be better to have similar functionality
> >> (scanning for VG's) for LVM in the kernel, instead of using a userland
> >> command?
>=20
> It is rather dangerous unless you have a separate kernel w/o LVM or
> a boot option (e.g., -lm) that allows booting with LVM turned off.
> Otherwise you can easily end up unable to reboot with a corrupt LVM
> system.
I don't get the point here. Why is it dangerous to move the VG scan from
vgscan into the kernel module? Why should this corrupt LVM? Can you
explain this in more detail?

Bye...

	Dirk
--=20
Dirk Heinrichs		| Tel:	+49 (0)241 413 260
Configuration Manager	| Fax:	+49 (0)241 413 2640
QIS Systemhaus GmbH	| Mail:	dheinrichs@qis-systemhaus.de
J=EF=BF=BDlicher Str. 338b	| Web:	http://www.qis-systemhaus.de
D-52070 Aachen		| ICQ#:	110037733