Hacker News new | ask | show | jobs
by dale_glass 1578 days ago
I think it was the --rebuild-tree argument, which as I understand tries to fix an otherwise completely broken filesystem by searching for anything that looks like metadata and gluing it back together.

I've not looked at reiserfs in many years though, so I could be mis-remembering here.

1 comments

Seems like something pretty fixable too... Only scan areas of the disk which aren't part of already valid filesystem structures, including the users files.
It's kind of the point of fsck that it scans areas of the disk which aren't part of already valid filesystem structures. It's what you run when your filesystem structure is invalid in order to recover as much as you can.
And then the user deletes that file, and it's not a part of a file anymore, but is still stored somewhere on a disk.
ResierFS allow metadata in everywhere. That’s how they allow sharing a ext2fs and resierfs on same disk during conversion