Filesystems can experience at least three different sorts of errors

Re:Filesystems can experience at least three different sorts... by rincebrain on Saturday March 12, 2022 @02:12PM (#30653935)

I think the difficulty in these conversations is that people say they want a "fsck for ZFS", when often they don't mean they want "periodic sanity checks for ZFS", they mean they want something like "xfs_repair -d* for ZFS" or "extundelete for ZFS" - that is, a tool for salvaging beyond-the-pale mangling such that your pool is no longer able to be imported.

* - not a perfect analogy, but I'm hard-pressed to think of good off the shelf tools for what they're looking for. I guess reiserfsck's infamously side-effect laden --rebuild-tree would probably be closest...

(I am acquainted with zdb -r and import -T; neither helps you if there's not enough metadata consistent to get enough of a pool structure in memory to 'import', but one could still conceivably salvage some data in that case.)

[ Parent | on HN ]

Re:Filesystems can experience at least three different sorts... by XorNot on Saturday March 12, 2022 @07:07PM (#30656440)

Technically this is the various, increasingly dangerous zfs import commands though.

The point of those is that the only time a pool is truly unusable is when you can't even import it.

[ Parent | on HN ]

Re:Filesystems can experience at least three different sorts... by rincebrain on Sunday March 13, 2022 @06:50AM (#30660088)

Yes, -F, -X, and -T.

The issue is, I think, people are expressing a desire for a tool that can still salvage data even when you've gone through all the (128/N) -T options and found them all unhelpful.

[ Parent | on HN ]