Date: Fri, 02 Aug 2013 21:21:44 +0200 From: =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= <lukasz@wasikowski.net> To: Volodymyr Kostyrko <c.kworr@gmail.com> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ZFS: can't read MOS of pool Message-ID: <51FC06C8.50906@wasikowski.net> In-Reply-To: <51FBCCC8.6040805@gmail.com> References: <51ED5B69.8050200@wasikowski.net> <51FBC24B.5030609@gmail.com> <51FBC4DC.4090506@wasikowski.net> <51FBC6F1.9030408@gmail.com> <51FBC8B3.4010304@wasikowski.net> <51FBCCC8.6040805@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
W dniu 2013-08-02 17:14, Volodymyr Kostyrko pisze: > 02.08.2013 17:56, Łukasz Wąsikowski wrote: >>> Can you also try what Trond suggests about boot order? You can also list >>> your boot fs in /boot/loader.conf like >> >> I listed ROOTFS in /boot/loader.conf, didn't helped. I'm using this boot >> order on 20+ boxes and never had any issues with it, but I'll check it >> as I don't have better idea what to do next. > > I'm almost out of suggestions... > > 1. Can you try to removing 'canmount' property from klawisz fs and > 'bootfs' property from pool? Property canmount is off for klawisz already. It's enabled for klawisz/ROOTFS though. I removed bootfs from the pool, didn't worked - can't read MOS. > 2. Can you try fetching late nexenta or illumos and give your pool a > full scrub? OpenIndiana's 151a7 scrub shows no error. > 3. Can you try disablng/enabling features? I assume you haven't used > compression and have no snapshots. I'm using lzjb compression on some not important for booting datasets (not on klawisz/ROOTFS) and I created some snapshots. -- best regards, Lukasz Wasikowski
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51FC06C8.50906>