If all you are doing is reading, the ZFS on-disk format is well documented and fairly easy to work with. Take a look at the ZFS bootloader code - that implements a ZFS reader in not too many lines of code and could easily be re-purposed for a recovery tool.
On 24 May 2012 09:04, Lev Serebryakov <l...@freebsd.org> wrote: > Hello, Steven. > You wrote 24 мая 2012 г., 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... > > > -- > // Black Lion AKA Lev Serebryakov <l...@freebsd.org> > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"