From owner-freebsd-bugs@freebsd.org Thu Jun 22 10:20:02 2017 Return-Path: Delivered-To: freebsd-bugs@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 21B64D889BB for ; Thu, 22 Jun 2017 10:20:02 +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 0E5CB75D8D for ; Thu, 22 Jun 2017 10:20:02 +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 v5MAK1nT088637 for ; Thu, 22 Jun 2017 10:20:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220203] [zfs] [panic] in dmu_objset_do_userquota_updates on mount Date: Thu, 22 Jun 2017 10:20:02 +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-bugs@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-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 10:20:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220203 --- Comment #2 from neovortex@gmail.com --- (In reply to Andriy Gapon from comment #1) Interesting - I tried to discover what that errno was, but came up blank. W= ith that in mind I imported the zpool unmounted and did a scrub (in hindsight, = my scrub is clean comment was before the issue appears, and after resolving it= by nuking the affected filesystem and restoring from backup). Bingo! CKSUM errors! pool: system-ssd state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://illumos.org/msg/ZFS-8000-8A scan: scrub repaired 0 in 0h12m with 1 errors on Thu Jun 22 10:02:50 2017 config: NAME STATE READ WRITE CKSUM system-ssd ONLINE 0 0 1 mirror-0 ONLINE 0 0 4 gpt/system-ssd1 ONLINE 0 0 4 gpt/system-ssd2 ONLINE 0 0 4 errors: Permanent errors have been detected in the following files: system-ssd/storage/ezjail/jailname:<0xfffffffffffffffe> I'm on a LSI SAS2008 card flashed to IT mode (unsure of exact version, "15" comes to mind though). The fact it's affected both disks is rather strange.= I have another zpool with HDDs on the same SAS card which hasn't had any issu= es (and is considerably larger), so TRIM might be a factor? I don't know enough about it, but seems strange if it is that to have killed both disks at once= if it was TRIM? How similar is the physical layout of blocks a mirrored pool between the disks? I think I might try moving the SSDs to the mainboard SATA controller (sadly only SATA 3Gb/s). I've used those disks with TRIM before in another system without issues, but not through a SAS2008 card. --=20 You are receiving this mail because: You are the assignee for the bug.=