Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Mar 2015 15:19:27 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 117158] [zfs] [panic] zpool scrub causes panic if geli vdevs detach on last close
Message-ID:  <bug-117158-8-KHoXfsggDQ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-117158-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-117158-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=117158

pjd@FreeBSD.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|freebsd-bugs@FreeBSD.org    |pjd@FreeBSD.org

Ben Woods <woodsb02@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |woodsb02@gmail.com

--- Comment #2 from pjd@FreeBSD.org ---
Responsible Changed
From-To: freebsd-bugs->pjd

I'll take this one.

--- Comment #3 from Ben Woods <woodsb02@gmail.com> ---
This bug bit me today - it is quite unnerving to watch your zpool go offline
due to unavailable devices, all from initiating a simply scrub!

However, I can confirm that a reboot recovered the zpool successfully, and
adding the following to /etc/rc.conf prevented it from happening again during
the next zpool scrub:
geli_autodetach="NO"

Note: I rebooted once more after adding that to /etc/rc.conf and before
initiating the next zpool scrub, just in case that configuration parameter is
only read at boot time or the time the geli is attached. Not sure if that was
required.

-- 
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-117158-8-KHoXfsggDQ>