From owner-freebsd-hackers@FreeBSD.ORG  Mon May 16 18:36:29 2011
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0024E1065674
	for <freebsd-hackers@freebsd.org>; Mon, 16 May 2011 18:36:28 +0000 (UTC)
	(envelope-from rank1seeker@gmail.com)
Received: from mail-bw0-f45.google.com (mail-bw0-f45.google.com
	[209.85.214.45])
	by mx1.freebsd.org (Postfix) with ESMTP id 7DF2D8FC1C
	for <freebsd-hackers@freebsd.org>; Mon, 16 May 2011 18:36:28 +0000 (UTC)
Received: by bwz16 with SMTP id 16so6042713bwz.18
	for <freebsd-hackers@freebsd.org>; Mon, 16 May 2011 11:36:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:message-id:from:to:subject:date:x-mailer;
	bh=tgGHYrUBuZIVIodmKYPjZVLIz2WPb95ydBx0rNqdZkw=;
	b=Bdd7Q3bfJ+NYuOvidQgAITo+k4Nc5RMHusURBZvXZDhAHJJy3Rg2olTym+bO33myED
	GITMzXNTV4zXn1pIl7L+gdwONWVHg9ZNCtS38dlzE6I2lpXskUd7ZaXunmjeTUq/he9i
	JJnsrrRASTssYb4QdHXluIC9UfyujnT8QztBw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:from:to:subject:date:x-mailer;
	b=XuAS44XBY+3O82YF09Rx/RWdw5bOk0Ht+cA+e1jgO70K6Rv9Ci5tNezl5nT5ov03FQ
	mp3B93rZIrddJgks8bF1m/L82NqU8xxmcI/ISOeGcIS+jsOwl24nztvyYo2QXuwmUVs7
	rZn5fuRVVS34Lx4iF5couXm/4MmtuA0FAdnQg=
Received: by 10.204.154.199 with SMTP id p7mr4368615bkw.114.1305570987157;
	Mon, 16 May 2011 11:36:27 -0700 (PDT)
Received: from DEV ([82.193.208.173])
	by mx.google.com with ESMTPS id c11sm3174281bkc.2.2011.05.16.11.36.11
	(version=SSLv3 cipher=OTHER); Mon, 16 May 2011 11:36:25 -0700 (PDT)
Message-ID: <20110516.183617.687.1@DEV>
From: rank1seeker@gmail.com
To: freebsd-hackers@freebsd.org
Date: Mon, 16 May 2011 20:36:17 +0200
X-Mailer: POP Peeper (3.7.0.0)
Subject: MD ROOT and image size limitation (makes kernel panic)
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2011 18:36:29 -0000

I have a 4 GB or ram, so why kernel panic with my MD ROOT, if larger then 
~40 MB?
I've tried to split up root in 20MB image and usr in 160 MB
Via loader.conf root becomes md0 and usr md1 and panic occurs even when 
they are split

I had to get rid of md1, to be able to boot with md0 as a root.

What exactly imposes limitation, inside kernel's code to SIZE of an image?
My hardware definatelly isn't ...

Is this different on amd64?
I've tested this, only with i386.


Domagoj S.