Date: Fri, 19 Sep 2014 10:32:41 +0200 From: Albert Shih <Albert.Shih@obspm.fr> To: Mike Carlson <mike@bayphoto.com> Cc: freebsd-fs@freebsd.org Subject: Re: Big problem with zfs.... Message-ID: <20140919083241.GA3353@pcjas.obspm.fr> In-Reply-To: <20140916225104.GA76997@pcjas.obspm.fr> References: <20140916165511.GA89818@pcjas.obspm.fr> <20140916171247.GB89818@pcjas.obspm.fr> <CA%2BKW7xQGC9jfHrc02PQ4zLhwDBCfOi6JZzBZ0Fdm8z-N%2Bz99tA@mail.gmail.com> <20140916225104.GA76997@pcjas.obspm.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 17/09/2014 à 00:51:04+0200, Albert Shih a écrit > Le 16/09/2014 à 12:29:01-0700, Mike Carlson a écrit So no one as any clue ? > > For obvious reasons, I am very interested in the forensic details of your > > panic. > > But I don't have lot of time this server is in production. So tomorrow I don't have to choice > to erase everything. In fact I manage to restart all service in a new disk array. So I'm going to keep this fail zpool under zdb So here what I did : 1/ Boot with live-cd of openindiana --> no succes the OS don't seem to find the device, all disk are always in « noconfigured » status. 2/ Boot with lice-cd of FreeBSD 11 --> Almost the same thing as with FreeBSD 10, the only difference is I don't get a kernel panic but just a Abort kernel trap. 3/ Put the disk array on some other FreeBSD 10 server --> same result kernel panic. 4/ Destroy /boot/zfs/zfs.cache, after that I'm able to start zfs without mounting the bad-zpool. So now because I can use the new disk array I restart all my service, and I launch in a screen the zdb -cbveL pool still....580 hours...before completed...:-( Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex France Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71 xmpp: jas@obspm.fr Heure local/Local time: ven 19 sep 2014 10:27:20 CEST
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140919083241.GA3353>