Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755682Ab0BPIq3 (ORCPT ); Tue, 16 Feb 2010 03:46:29 -0500 Received: from tritonia.xxlwebhosting.nl ([81.4.88.63]:45597 "EHLO tritonia.xxlwebhosting.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750759Ab0BPIq1 (ORCPT ); Tue, 16 Feb 2010 03:46:27 -0500 Message-ID: <4B7A5B5B.6040307@grumpydevil.homelinux.org> Date: Tue, 16 Feb 2010 09:46:19 +0100 From: Rudy Zijlstra User-Agent: Thunderbird 2.0.0.23 (X11/20090820) MIME-Version: 1.0 To: "H. Peter Anvin" CC: david@lang.hm, Neil Brown , Michael Evans , Justin Piszcz , linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Linux mdadm superblock question. References: <4877c76c1002111752h23e14f7aibe58a89181e6f493@mail.gmail.com> <4B77044B.1020609@zytor.com> <20100216112708.4a863f86@notabene.brown> <4B79F3CE.5030907@zytor.com> <4B7A42EB.3070405@zytor.com> In-Reply-To: <4B7A42EB.3070405@zytor.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ACL-Warn: { X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - tritonia.xxlwebhosting.nl X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - grumpydevil.homelinux.org X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1696 Lines: 43 H. Peter Anvin wrote: > On 02/15/2010 07:18 PM, david@lang.hm wrote: >> On Mon, 15 Feb 2010, H. Peter Anvin wrote: >> >>> On 02/15/2010 04:27 PM, Neil Brown wrote: >>> >>> There are three options: >>> >>> a) either don't boot from it (separate /boot); >>> b) use a bootloader which installs in the MBR and >>> hopefully-unpartitioned disk areas (e.g. Grub); >>> c) use a nonstandard custom MBR. >>> >>> Neither (b) or (c), of course, allow for chainloading from another OS >>> install and thus are bad for interoperability. >> >> I have had no problems with XFS partitions and lilo as the bootloader. >> I've been doing this for a couple of years now without realizing that >> there is supposed to be a problem. >> > > LILO also can be stuffed in the MBR (and then uses block-pointers from > there). There is one more option that I didn't mention, which is to > put the bootloader of a separate partition, OS/2 style. Again, breaks > the standard chainloading model. There is another configuration that fails. Use partitioned md. I do not think it matters whether over whole device or with a partition table. Neither grub nor lilo will boot off from it. I've tested that exensively with a partition on the disks. I am using PXE boot to boot 2 servers with that configuration. That adds a dependency on the pxe boot server, but considering the function of those servers they are moot if that pxe server is dead anyways.... Cheers, Rudy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/