Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Jun 2017 10:20:02 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 220203] [zfs] [panic] in dmu_objset_do_userquota_updates on mount
Message-ID:  <bug-220203-8-ptEOWpLLHg@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-220203-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-220203-8@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
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.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220203-8-ptEOWpLLHg>