From owner-freebsd-fs@freebsd.org Wed Jul 5 14:03:12 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91D2ADABE94 for ; Wed, 5 Jul 2017 14:03:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 803B281D62 for ; Wed, 5 Jul 2017 14:03:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v65E3CwV049361 for ; Wed, 5 Jul 2017 14:03:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 220203] [zfs] [panic] in dmu_objset_do_userquota_updates on mount Date: Wed, 05 Jul 2017 14:03:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: neovortex@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2017 14:03:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220203 --- Comment #6 from neovortex@gmail.com --- So since moving the SSDs from the SAS2008 controller to the mainboard SATA controller this issue hasn't reoccurred again. Considering the frequency it= was reoccurring previously, I'd say that's done the trick. I guess this issue really has two parts, one is what's causing corruption w= ith SSDs on the SAS2008 controller (my guess being TRIM related), bug in FreeBS= D, bug in SAS2008 firmware, or bug in SSD firmware that only gets triggered wh= en on a SAS2008 controller, but not on other controllers. For completeness, the SSDs are the following: =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D Model Family: Marvell based SanDisk SSDs Device Model: SanDisk SDSSDHII480G Serial Number: xxx LU WWN Device Id: xxx Firmware Version: X31200RL User Capacity: 480,103,981,056 bytes [480 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 T13/2015-D revision 3 SATA Version is: SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Wed Jul 5 23:56:36 2017 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D The second issue I guess is when a filesystem has corrupt metadata if it co= uld be handled more gracefully, eg zfs mount returns an error rather than causi= ng a panic. I'm not sure how practical this is, but it was an unusual experience having on-disk corruption causing a panic compared to the behaviour of other filesystems. --=20 You are receiving this mail because: You are the assignee for the bug.=