See https://github.com/alcarithemad/zfsp — zfs in python. May be use this as a *starting point* to build an interactive zpool/zfs explore tool?
On Apr 30, 2019, at 3:14 AM, Michelle Sullivan <miche...@sorbs.net> wrote: >> Speaking for a tool like 'fsck': I think I'm mostly convinced that it's not >> necessary, because at the point ZFS says the metadata is corrupted, it means >> that these metadata was really corrupted beyond repair (all replicas were >> corrupted; otherwise it would recover by finding out the right block and >> rewrite the bad ones). > > I see this message all the time and mostly agree.. actually I do agree with > possibly a minor exception, but so minor it’s probably not worth it. However > as I suggested in my original post.. the pool says the files are there, a > tool that would send them (aka zfs send) but ignoring errors to spacemaps etc > would be real useful (to me.) > >> >> An interactive tool may be useful (e.g. "I saw data structure version 1, 2, >> 3 available, and all with bad checksum, choose which one you would want to >> try"), but I think they wouldn't be very practical for use with large data >> pools -- unlike traditional filesystems, ZFS uses copy-on-write and heavily >> depends on the metadata to find where the data is, and a regular "scan" is >> not really useful. > > Zdb -AAA showed (shows) 36m files.. which suggests the data is intact, but > it aborts the mount with I/o error because it says metadata has three > errors.. 2 ‘metadata’ and one “<storage:0x0>” (storage being the pool name).. > it does import, and it attempts to resilver but reports the resilver finishes > at some 780M (ish).. export import and it does it all again... zdb without > -AAA aborts loading metaslab 122. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
