From owner-freebsd-stable Fri Jan 5 5:12:47 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 05:12:44 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 7129237B6A0 for ; Fri, 5 Jan 2001 05:12:44 -0800 (PST) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: postfix [port 2741]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <113655-220>; Fri, 5 Jan 2001 14:12:34 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 9647213631; Fri, 5 Jan 2001 14:12:24 +0100 (CET) From: Daniel Lang To: dxoch , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum Question Message-ID: <20010105141224.E17176@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A55B92E.A570E938@escape.gr> X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Sender: langd@informatik.tu-muenchen.de Date: Fri, 5 Jan 2001 14:12:25 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Jim, [..] > Is there is any chance that vinum-related options in the loader.conf > (vinum_load ="YES") > can help me to boot from a vimum volume, or this is completely > irrelevant? I guess so. I know of 'vinum_load="YES"' only in /etc/rc.conf, not loader.conf or kernel.conf. Although I guess you could immediately load the vinum.ko, before booting the kernel (i.e. load the kernel, load the module along with other modules like splash, then boot the kernel), but this does not help you to boot from a vinum device. The problem is, that in FreeBSD, the bootstrap loaders and the kernel reside in the root-partition. The booting process is described very good in http://www.freebsd.org/handbook/boot.html You will notice that each stage just knows as much about the the disks/filesystem as it needs. So boot1 knows about the disklabel and slices to find boot2 boot2 knows about about UFS/FFS to find /boot/loader or /kernel. Themselves they reside in the MBR, or the boot-sector of the slice. Although loader is more sophisticated, it does not know about vinum, too. The first thing to know about vinum is the kernel with the vinum module loaded. In order to really boot from a vinum device, previous stages also have to know (at least something) about vinum devices. This is not the case, and I guess very difficult to implement. If you look at other OSes which allow booting from managed volumes, you may notice, that they have a special boot-filesystem (e.g. /stand, /boot), which must meet certain requirements, (like contigous block allocation, the first partition on disk/slice, etc). I guess it would be really painful to try to provide this functionality, with many drawbacks (I guess most in code-stability), huge effort required and little advantages. If you need average security agains disk-crashes, you can keep your data in vinum-volumes and back up the root-partition on a regular basis e.g. with dd. If you really need more security, go and buy a SCSI-SCSI raid-controller, which is seen as one or more single disks, independent of its real disks and configuration. You save yourself lots of trouble. Ok, this is just my opinion, based on some experience. Best regards, Daniel -- IRCnet: Mr-Spock - Burn them to ashes, then burn the ashes. - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message