Date: Thu, 24 May 2012 12:04:21 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: "Steven Hartland" <killing@multiplay.co.uk> Cc: freebsd-current FreeBSD <freebsd-current@freebsd.org> Subject: Re: UFS+J panics on HEAD Message-ID: <1239922227.20120524120421@serebryakov.spb.ru> In-Reply-To: <8D72700F5CA4461BAD1C98908689CB9E@multiplay.co.uk> References: <38A5BC8F-A8FB-4371-AB1D-9548F5957254@lists.zabbadoz.net><20120523131046.GC2358@deviant.kiev.zoral.com.ua> <12410676034.20120524013853@serebryakov.spb.ru> <8D72700F5CA4461BAD1C98908689CB9E@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Steven. You wrote 24 =D0=BC=D0=B0=D1=8F 2012 =D0=B3., 1:58:48: SH> While it might be a shame to see FFS go by the wayside are there any SH> big reasons why you would rather stick with FFS instead of moving SH> to ZFS with all the benefits that brings? I afraid, that after real hardware failure (like real HDD death, not these pseudo-broken-hardware situations, when HDDs is perfectly alive and in good condition), all data will be lost. I could restore data from remains of FFS by hands (format is straightforward and well-known), but ZFS is different story... And all these messages about panics after pool import... Yes, it could be result of REAL hardware problems, but I want to have some hope to restore some of the data after such crashes. Yes, backups is solution, but I don't have money to buy (reliable) hardware to backup 4Tb of data :( I attended "Solaris internals" 5-days training four years ago (when I worked for Sun Microsystems), and instructor says same words... --=20 // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1239922227.20120524120421>