Date: Sun, 27 Jan 2013 21:52:20 +0900 From: Alexander Nedotsukov <bland@FreeBSD.org> To: Pawel Jakub Dawidek <pjd@FreeBSD.org>, "hselasky@FreeBSD.org" <hselasky@FreeBSD.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, "freebsd-usb@freebsd.org" <freebsd-usb@freebsd.org> Subject: Re: ZFS + usb in trouble? Message-ID: <845D0D19-7191-4EDD-8EDE-1331E13821CB@FreeBSD.org> In-Reply-To: <20130123134601.GB53514@garage.freebsd.pl> References: <B9569401-6A19-437C-82D8-794022D42CF1@bbnest.net> <20130121205851.GB1341@garage.freebsd.pl> <20130121211718.GD1341@garage.freebsd.pl> <B3A22592-7AB4-4070-9B57-7234A70071F2@bbnest.net> <20130122181012.GD1714@garage.freebsd.pl> <B14908B2-A116-47E8-A311-E378E82924C6@FreeBSD.org> <20130123134601.GB53514@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you, Pawel. Hans, can please you take a look at your commits done on Dec 20 (r244500 = and r244503)? They are seems to be the culprit. On 23.01.2013, at 22:46, Pawel Jakub Dawidek <pjd@FreeBSD.org> wrote: > On Wed, Jan 23, 2013 at 09:11:23PM +0900, Alexander Nedotsukov wrote: >> And now both are failing, although zfs in a different way. >=20 > Yes, but now we are sure this is not ZFS issue. Sequential read simply > doesn't trigger the corruption, but ZFS access patterns do. The read > errors you are seeing are due to GELI returning EIO on integrity > verification error. >=20 >> # zpool status >> pool: testpool >> state: ONLINE >> status: One or more devices has experienced an unrecoverable error. = An >> attempt was made to correct the error. Applications are = unaffected. >> action: Determine if the device needs to be replaced, and clear the = errors >> using 'zpool clear' or replace the device with 'zpool replace'. >> see: http://illumos.org/msg/ZFS-8000-9P >> scan: scrub repaired 1M in 0h2m with 0 errors on Wed Jan 23 20:57:11 = 2013 >> config: >>=20 >> NAME STATE READ WRITE CKSUM >> testpool ONLINE 0 0 0 >> raidz1-0 ONLINE 0 0 0 >> da5.elid ONLINE 0 0 0 >> da5.elie ONLINE 21 0 0 >> da5.elif ONLINE 0 0 0 >>=20 >> # dmesg | tail -20 >> GEOM_ELI: da1.eli: Failed to authenticate 131072 bytes of data at = offset 1010827264. >> ath0: bb hang detected (0x4), resetting >> GEOM_ELI: Device da5.eli created. >> GEOM_ELI: Encryption: AES-XTS 128 >> GEOM_ELI: Integrity: HMAC/SHA1 >> GEOM_ELI: Crypto: software >> GEOM_ELI: da5.eli: Failed to authenticate 4096 bytes of data at = offset 4096. >> GEOM_ELI: da5.eli: Failed to authenticate 4096 bytes of data at = offset 0. >> GEOM_ELI: da5.eli: Failed to authenticate 5792 bytes of data at = offset 229288288. >> GEOM_ELI: da5.eli: Failed to authenticate 65536 bytes of data at = offset 229429248. >> GEOM_ELI: da5.eli: Failed to authenticate 131072 bytes of data at = offset 229298176. >> GEOM_ELI: da5.eli: Failed to authenticate 26496 bytes of data at = offset 229494784. >> GEOM_ELI: da5.eli: Failed to authenticate 12288 bytes of data at = offset 270299136. >> GEOM_ELI: da5.eli: Failed to authenticate 65536 bytes of data at = offset 270319616. >> GEOM_ELI: da5.eli: Failed to authenticate 5792 bytes of data at = offset 273095488. >> GEOM_ELI: da5.eli: Failed to authenticate 56864 bytes of data at = offset 273105376. >> GEOM_ELI: da5.eli: Failed to authenticate 2400 bytes of data at = offset 273326080. >> GEOM_ELI: da5.eli: Failed to authenticate 65536 bytes of data at = offset 272560128. >> GEOM_ELI: da5.eli: Failed to authenticate 131072 bytes of data at = offset 272429056. >> GEOM_ELI: da5.eli: Failed to authenticate 32768 bytes of data at = offset 272396288. >=20 > --=20 > Pawel Jakub Dawidek http://www.wheelsystems.com > FreeBSD committer http://www.FreeBSD.org > Am I Evil? Yes, I Am! http://tupytaj.pl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?845D0D19-7191-4EDD-8EDE-1331E13821CB>