Date: Thu, 26 May 2011 18:57:03 +0200 From: rank1seeker@gmail.com To: freebsd-hackers@freebsd.org Subject: Re: MD ROOT and image size limitation (makes kernel panic) Message-ID: <20110526.165703.671.1@DEV> In-Reply-To: <BANLkTimQV%2B19g=9TbHCNq1VbDUFoWVaB4Q@mail.gmail.com> References: <20110516.183617.687.1@DEV> <BANLkTimQV%2B19g=9TbHCNq1VbDUFoWVaB4Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok now, all works great IF md root, isn't statically compiled, into the = kernel.=0D=0A=0D=0AWhen I statically compile it, into the kernel, I get = ROOT MOUNT error.=0D=0AWhen I list available devices via '?', md0 does = exist!=0D=0A=0D=0AI point mountroot to it, but nada, I get MOUNT ROOT = ERROR.=0D=0AI've tried to statically compile, BOTH gzip-ed image (~87 Mb) = and non compressed image (~197 Mb), of md root.=0D=0A=0D=0AWith both, md0 = exist at mountroot, but when manually pointed to md0, I get MOUNT ROOT = ERROR=0D=0A=0D=0AIs this a bug?=0D=0AAs it doesn't expect so huge kernel = of i.e; ~220 Mb=0D=0A=0D=0AJust to say, that md0, DOESN'T have a = partition or bsdlabel, just UFS=0D=0A=0D=0A=0D=0ADomagoj Smol=E8i=E6
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110526.165703.671.1>