Date: Sun, 29 Jul 2012 17:19:45 -0400 From: Michael Butler <imb@protected-networks.net> To: Alexander Motin <mav@FreeBSD.org> Cc: current@freebsd.org Subject: Re: post SVN r238886 no boot? Message-ID: <5015A8F1.70808@protected-networks.net> In-Reply-To: <50159969.7000008@FreeBSD.org> References: <501575A0.2080007@protected-networks.net> <CAGH67wTJ4uOEAO-sdoUAUhpAgzTPXv-kDxKD1y_6f0nxt0_U0g@mail.gmail.com> <5015829C.6060508@protected-networks.net> <CAGH67wROQyjTw7A8inHKzsLDs2-1U%2BCaU=tiUez1T1YJNzTo7A@mail.gmail.com> <501588B7.6000902@protected-networks.net> <CAGH67wQ00n1Supeghn_Z0ihA0D4iA-w=Tb35Xt%2BYcNLGYt=UqA@mail.gmail.com> <50158BBA.5060206@FreeBSD.org> <345962186.20120729235239@serebryakov.spb.ru> <50159969.7000008@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/29/12 16:13, Alexander Motin wrote: > I was able to diagnose problem and it is not related to CAM as I've > thought initially. It is related to GEOM spoiling mechanism. > > During boot process fsck opens checked disks for writing, while root at > that time mounted as read-only. Disks close by fsck causes spoiling of > the root partition's GEOM VFS, that with r238886 change made it > inaccessible. > > I've reverted that GEOM VFS change at r238892, that should fix the > problem until better solution will be found. I can confirm that this change avoids/fixes the issue - thanks :-) > I'm sorry. No apology required - if I'm running -current, I should and do expect the occasional breakage. It's better found now than when it hits a wider release, i.e. I don't put -current on a production box .. imb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAVqPAACgkQQv9rrgRC1JLfagCgzA7Rxtq7Sy4ps6CR0AaqDIvT Nh0AoKX+xn3KjEUjQy3SHWyA8vhvCSwe =65il -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5015A8F1.70808>