Date: Sat, 4 May 2019 12:51:12 -0700 From: Bakul Shah <bakul@bitblocks.com> To: Michelle Sullivan <michelle@sorbs.net> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: ZFS... Message-ID: <36C9B52C-D832-42B3-B4A8-566B89784982@bitblocks.com> In-Reply-To: <5ED8BADE-7B2C-4B73-93BC-70739911C5E3@sorbs.net> References: <30506b3d-64fb-b327-94ae-d9da522f3a48@sorbs.net> <CAOtMX2gf3AZr1-QOX_6yYQoqE-H%2B8MjOWc=eK1tcwt5M3dCzdw@mail.gmail.com> <56833732-2945-4BD3-95A6-7AF55AB87674@sorbs.net> <3d0f6436-f3d7-6fee-ed81-a24d44223f2f@netfence.it> <17B373DA-4AFC-4D25-B776-0D0DED98B320@sorbs.net> <70fac2fe3f23f85dd442d93ffea368e1@ultra-secure.de> <70C87D93-D1F9-458E-9723-19F9777E6F12@sorbs.net> <CAGMYy3tYqvrKgk2c==WTwrH03uTN1xQifPRNxXccMsRE1spaRA@mail.gmail.com> <5ED8BADE-7B2C-4B73-93BC-70739911C5E3@sorbs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
See https://github.com/alcarithemad/zfsp =E2=80=94 zfs in python. May be use this as a *starting point* to build an interactive zpool/zfs expl= ore tool? On Apr 30, 2019, at 3:14 AM, Michelle Sullivan <michelle@sorbs.net> wrote: >> Speaking for a tool like 'fsck': I think I'm mostly convinced that it's n= ot necessary, because at the point ZFS says the metadata is corrupted, it me= ans that these metadata was really corrupted beyond repair (all replicas wer= e corrupted; otherwise it would recover by finding out the right block and r= ewrite the bad ones). >=20 > I see this message all the time and mostly agree.. actually I do agree wit= h possibly a minor exception, but so minor it=E2=80=99s probably not worth i= t. 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 sp= acemaps etc would be real useful (to me.) >=20 >>=20 >> 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 p= ools -- unlike traditional filesystems, ZFS uses copy-on-write and heavily d= epends on the metadata to find where the data is, and a regular "scan" is no= t really useful. >=20 > Zdb -AAA showed (shows) 36m files.. which suggests the data is intact, bu= t it aborts the mount with I/o error because it says metadata has three erro= rs.. 2 =E2=80=98metadata=E2=80=99 and one =E2=80=9C<storage:0x0>=E2=80=9D (s= torage being the pool name).. it does import, and it attempts to resilver bu= t reports the resilver finishes at some 780M (ish).. export import and it do= es it all again... zdb without -AAA aborts loading metaslab 122.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36C9B52C-D832-42B3-B4A8-566B89784982>