Date: Sun, 31 Oct 2010 12:41:50 +0100 From: Thomas Zander <thomas.e.zander@googlemail.com> To: freebsd-fs@freebsd.org Subject: Re: ZFS inresponsive. Message-ID: <AANLkTi=vKSC_wULSzd9k2hF-gDTVeseqyzWrKHsAOMd2@mail.gmail.com> In-Reply-To: <20101031104209.771cc47e@r500.local> References: <BE2EF896-4990-4A75-9DD4-B0534DFE0B71@pean.org> <20101031104209.771cc47e@r500.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 31, 2010 at 10:42, Fabian Keil <freebsd-listen@fabiankeil.de> wrote: > Oct 18 18:33:05 r500 kernel: GEOM_ELI: Crypto WRITE request failed (error=5). label/poppstar.eli[WRITE(offset=362645020672, length=131072)] Same here, same setup. ZFS, GELI, USB. Occasionally this happens, haven't found a way to reliably trigger it yet. However, what seems to (more or less) reliably work is to trigger a failed crypto READ request when copying files from a ZFS-GELI-USB pool to a FAT formatted USB stick. If that happens, I have to reboot as the ZFS-GELI-USB pool is no longer functioning properly. This is on a recent 8-STABLE amd64 box, but it has always been that way since I am using zpools on USB disks on FreeBSD. Riggs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=vKSC_wULSzd9k2hF-gDTVeseqyzWrKHsAOMd2>