From owner-freebsd-fs@FreeBSD.ORG Fri Aug 31 08:25:57 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FBD4106566B for ; Fri, 31 Aug 2012 08:25:57 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mx1.freebsd.org (Postfix) with ESMTP id B63598FC12 for ; Fri, 31 Aug 2012 08:25:54 +0000 (UTC) Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0LwVKN-1TgJDY33nj-018NHP; Fri, 31 Aug 2012 10:25:47 +0200 Message-ID: <5040750D.5070109@brockmann-consult.de> Date: Fri, 31 Aug 2012 10:25:49 +0200 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <503FD9F3.6040205@pobox.com> <504063FC.1080408@pobox.com> In-Reply-To: <504063FC.1080408@pobox.com> X-Enigmail-Version: 1.4.4 X-Provags-ID: V02:K0:4KVrgDgL/Oyg57KDlLVk3qq15CvBveLgD6GbRNXssW8 HE4tVdBgOVdlrQxXEdY+0j8PJ+p8VqyOTDnVhvhLAwWoaSJlkP 4RVmvwAoNC9V60shj3pSiTlNVhRBKo5CHbDOvHNgK7Qsin0Dy5 mOPZ98D8ZKwhsolpTsPX4uJ5FrDF5vG+G28uHiQxZQXAzBenEK VQx0MKSh1Hc2ybyVteO4rD0owJ0MNazJsvhBa0//4Gk2M6Tc81 B2S2WZvYPCJNOwC7UiA5/wYPTh8KvOvhhlnBQ2PqOJ5j/cc4P6 fW2qlwNXKwl8DJntvTqrg933brXMjw0cPFN+5skkDVP+NryPrw 82UsVAqzTmhFANhe5l29nXrfZMydkJvxeG4KK098U Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: zfs woes X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2012 08:25:57 -0000 The mailing list strips attachments. We still don't have your image. And as prevention, I would say test your disks and upgrade the firmware. I had a similar problem (panics when both root disks were gone, checksum errors on boot) with Crucial SSDs, but new firmware fixed it. Sebulon on the forum had an issue with some Samsung disks or some SSDs and I believe fixed it the same way. I test my disks by putting them in a redundant test zpool, writing to them, then pulling one, putting back in, pulling again, and putting back in, and then testing to see if the disk can be seen. It seems to work in detecting the problem on those SSDs, but I don't have any other disks that I've tested with time in the OS. (btw warning #1 if you do this non-redundant, your writing process will lock up, and the zpool command might too, so you can't as easily test multiple disks, and warning #2 gpart show on the disk you pulled and broke will segfault, and gpart recover will panic the system) As for a fix after your system is already damaged... sorry, don't know. On 08/31/2012 09:13 AM, Duncan Young wrote: > My apologies, I forgot to attach an image of the output from the panic. > > Duncan > > On 31/08/2012 7:24 AM, Duncan Young wrote: >> Hi All, >> >> I have a problem. >> >> My computer has been regularly locking up, I think it could be disk >> related. This has been causing the odd >> checksum error on the disks, which scrubbing seems to clean up. >> >> Now my problem is, after starting up after one of these lockups, the >> system mirror, reported an uncorrectable error. >> Both drives showed checksum errors (4 errors, I think). Using the -v >> flag a file was identified as corrupt. Upon trying >> to delete this file, the system panicked. O.K. it is on the >> system/ports filesystem, so I'll just copy all but the corrupt >> directory, to system/ports2 etc, etc. Upon zfs destroy -r >> system/ports, another panic. Now the entire system pool is corrupted, >> resulting in a panic upon boot. I presume the reslivering is causing >> this. >> >> I moved the two disks to my backup machine (purely used for sending >> backups onto). Its running 9.0-release #2. When I try to do >> an import, it panics. Now this I find surprising. Surely importing >> disks should either succeed or fail, not bring the whole machine down. >> >> Trying to import into openindiana also causes a panic and reboot (I >> didn't expect this). >> >> Any pointers as to where I go from now (other than reinstall). >> >> Duncan >> >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" -- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.maloney@brockmann-consult.de Internet: http://www.brockmann-consult.de --------------------------------------------