[Bug 205882] [zfs] can't import l2arc devices by guid after r292066

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jan 4 16:20:34 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205882

            Bug ID: 205882
           Summary: [zfs] can't import l2arc devices by guid after r292066
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: asomers at FreeBSD.org
          Reporter: asomers at FreeBSD.org
                CC: delphij at FreeBSD.org, freebsd-amd64 at FreeBSD.org
                CC: freebsd-amd64 at FreeBSD.org

r292066 makes vdev_geom more careful about what devices it will open.  It fixed
a bug with booting from ZFS when the device order has changed.  However,
delphij points out that it breaks importing l2arc devices by guid, because
l2arc devices' labels lack a pool guid.  The following sequence of commands
will reproduce the failure:

zpool create -f withcache mirror da0 da2 cache da3
zpool export withcache
# remove da1 and da3, then reinsert da3.  It should now be called da1
zpool import withcache
# zpool status withcache
  pool: withcache
 state: ONLINE
status: One or more devices could not be opened.  Sufficient replicas exist for
        the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
   see: http://illumos.org/msg/ZFS-8000-2Q
  scan: none requested
config:

        NAME                    STATE     READ WRITE CKSUM
        withcache               ONLINE       0     0     0
          mirror-0              ONLINE       0     0     0
            da0                 ONLINE       0     0     0
            da2                 ONLINE       0     0     0
        cache
          13126929149130124089  UNAVAIL      0     0     0  was /dev/da3

errors: No known data errors

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-amd64 mailing list