Date: Sat, 19 Jul 2008 12:50:50 +0200 From: "Daniel Eriksson" <daniel_k_eriksson@telia.com> To: "freebsd-stable" <freebsd-stable@freebsd.org> Cc: Alex Trull <alex@trull.org> Subject: RE: Panic on ZFS startup after crash Message-ID: <4F9C9299A10AE74E89EA580D14AA10A61A197B@royal64.emp.zapto.org> In-Reply-To: <1216459022.6521.6.camel@porksoda> References: <4F9C9299A10AE74E89EA580D14AA10A61A197A@royal64.emp.zapto.org> <1216459022.6521.6.camel@porksoda>
next in thread | previous in thread | raw e-mail | index | archive | help
Alex Trull wrote: > I've tried neither of these in your particular case, but they might be > worth a try: >=20 > Just a suggestion, but try specify vfs.zfs.zil_disable=3D1 or=20 > as a kernel > variable in the boot cli. >=20 > You may want to try export and import the pool and see how it likes it > then. I considered disabling the zil but didn't think it would make a difference (because zfs will most likely check if there is any data in zil on startup anyway). I'll try it though! Importing the pool results in the exact same problem. (I couldn't export the live pool because the box paniced, but by making sure the vdev was unavailable on zfs startup I could export the stale pool, enable the vdev (by doing a "geli attach") and then I tried to import the pool. No luck, same panic message. ___ Daniel Eriksson (http://www.toomuchdata.com/)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F9C9299A10AE74E89EA580D14AA10A61A197B>