From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 12:11:30 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 51009347; Wed, 23 Jan 2013 12:11:30 +0000 (UTC) (envelope-from bland@FreeBSD.org) Received: from mail2.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.freebsd.org (Postfix) with ESMTP id 20DA4D83; Wed, 23 Jan 2013 12:11:30 +0000 (UTC) Received: from eee.bbnest.net (w133033.ppp.asahi-net.or.jp [121.1.133.33]) by mail2.asahi-net.or.jp (Postfix) with ESMTP id A958D19781; Wed, 23 Jan 2013 21:11:28 +0900 (JST) Received: from nest.bbnest.net (nest.bbnest.net [192.168.1.108]) (authenticated bits=0) by eee.bbnest.net (8.14.6/8.14.5) with ESMTP id r0NCBLNe097795 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 23 Jan 2013 21:11:22 +0900 (JST) (envelope-from bland@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: ZFS + usb in trouble? From: Alexander Nedotsukov In-Reply-To: <20130122181012.GD1714@garage.freebsd.pl> Date: Wed, 23 Jan 2013 21:11:23 +0900 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130121205851.GB1341@garage.freebsd.pl> <20130121211718.GD1341@garage.freebsd.pl> <20130122181012.GD1714@garage.freebsd.pl> To: Pawel Jakub Dawidek X-Mailer: Apple Mail (2.1499) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Wed Jan 23 21:11:28 2013 X-DSPAM-Confidence: 0.9996 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 50ffd370977962915317530 Cc: FreeBSD Current , hselasky@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2013 12:11:30 -0000 On 23.01.2013, at 3:10, Pawel Jakub Dawidek wrote: > On Tue, Jan 22, 2013 at 11:47:29PM +0900, Alexander Nedotsukov wrote: >> Hi Pawel, >>=20 >> Here what I did. >>=20 >> # geli onetime -a hmac/sha1 -s 4096 /dev/da5=20 >> # dmesg | tail -15 >> wlan0: link state changed to UP >> ugen5.4: at usbus5 >> umass2: on usbus5 >> umass2: SCSI over Bulk-Only; quirks =3D 0x0100 >> umass2:4:2:-1: Attached to scbus4 >> da5 at umass-sim2 bus 2 scbus4 target 0 lun 0 >> da5: Removable Direct Access SCSI-2 device=20 >> da5: 40.000MB/s transfers >> da5: 983MB (2015231 512 byte sectors: 64H 32S/T 983C) >> 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. >>=20 >> # dd if=3D/dev/random of=3D/dev/da5.eli bs=3D1m >> dd: /dev/da5.eli: short write on character device >> dd: /dev/da5.eli: end of device >> 875+0 records in >> 874+1 records out >> 917151744 bytes transferred in 1530.831674 secs (599120 bytes/sec) >>=20 >> # dd if=3D/dev/da5.eli of=3D/dev/null bs=3D1m >> 874+1 records in >> 874+1 records out >> 917151744 bytes transferred in 178.874312 secs (5127353 bytes/sec) >>=20 >> All clear. No new errors. >>=20 >> Zpool created on the same usb stick is still failing with cksum = errors. >>=20 >> # usbconfig -d 5.4 add_quirk UQ_MSC_NO_SYNC_CACHE >>=20 >> umass2: SCSI over Bulk-Only; quirks =3D 0x4000 >>=20 >> Re-created zpool is still failing with cksum errors. Every new scrub = run is triggering another "repairing". >=20 > Interesting. Can you put ZFS on top of GELI with authentication after > filling da0.eli with random random and see if GELI will report > corruption when ZFS will or if only ZFS will report corruption? And now both are failing, although zfs in a different way. # 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: 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 # 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.