Date: Thu, 09 Jun 2011 12:41:14 +0300 From: Daniel Kalchev <daniel@digsys.bg> To: freebsd-fs@freebsd.org Subject: Re: zfs mirror: 1 disk lost, corrupted other disk. crashes zfs tools and panics system Message-ID: <4DF0953A.9030002@digsys.bg> In-Reply-To: <SNT105-W34F47DC90A1802CC68B0FBE6620@phx.gbl> References: <SNT105-W34F47DC90A1802CC68B0FBE6620@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09.06.11 01:32, Edward Sutton wrote: [...] > pool: zroot > state: FAULTED > status: An intent log record could not be read. > Waiting for adminstrator intervention to fix the faulted pool. > action: Either restore the affected device(s) and run 'zpool online', > or ignore the intent log records by running 'zpool clear'. > see: http://www.sun.com/msg/ZFS-8000-K4 > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > zroot FAULTED 0 0 0 bad intent log > mirror DEGRADED 0 0 0 > gpt/disk0 ONLINE 0 0 0 > gpt/disk1 UNAVAIL 0 0 0 cannot open > > Going by my memory here: It fails to boot with "ROOT MOUNT ERROR". I had luck with `zpool clear, removing disk1, and mounting all pool partitions. Data could be copied off but some filesystems were missing and attempts to list all snapshots segfaults. Every export/import requires a zpool clear. Attempting a scrub lead to a panic on every import on the pool thereafter. Tried a -current snapshot (FreeBSD-9.0-CURRENT-201105-amd64-dvd1.iso) livecd mode with similar panic results to 8.2-release. > Perhaps you should try to use zpool import -F zroot from an ZFS v28 system, such as the FreeBSD-9.0-CURRENT you mentioned? Daniel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DF0953A.9030002>