Date: Tue, 16 Nov 2010 20:41:47 -0500 (EST) From: Terry Kennedy <TERRY@tmk.com> To: Michael DeMan <freebsd@deman.com> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ZFS panic after replacing log device Message-ID: <01NUC6V4LBAQ00BNN4@tmk.com> In-Reply-To: "Your message dated Mon, 15 Nov 2010 23:48:26 -0800" <816D59CD-1BAF-4331-BEAD-67CEADCE4EF9@deman.com> References: <01NUB1F8POL000BNN4@tmk.com> <01NUB3IOMZJW00BNN4@tmk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I would say it is definitely very odd that writes are a problem. Sounds
> like it might be a hardware problem. Is it possible to export the pool,
> remove the ZIL and re-import it? I myself would be pretty nervous trying
> that, but it would help isolate the problem? If you can risk it.
I think it is unlikely to be a hardware problem. While I haven't run any
destructive testing on the ZFS pool, the fact that it can be read without
error, combined with ECC throughout the system and the panic always happen-
ing on the first write, makes me think that it is a software issue in ZFS.
When I do:
zpool export data; zpool remove data da0
I get a "No such pool: data". I then re-imported the pool and did:
zpool offline data da0; zpool export data; zpool import data
After doing that, I can write to the pool without a panic. But once I
online the log device and do any writes, I get the panic again.
As I mentioned, I have this data replicated elsewere, so I can exper-
iment with the pool if it will help track down this issue.
Terry Kennedy http://www.tmk.com
terry@tmk.com New York, NY USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01NUC6V4LBAQ00BNN4>