We have a script that adds corruption to ext2/3/4 filesystems and runs
e2fsck on it. It definitely could be improved, but it still catches some
It tries to format the filesystem with different features and options, then
adds corruption from both random data and copying parts of the
filesystem internally to some other part of the filesystem. It might be useful to corrupt some random bits and bytes in the filesystem also,
but it doesn't do that today.
There is also fsfuzzer, which writes random data to the filesystem and
tries to mount it, but I don't know if that has been tried with e2fsck.
The other major question I have is why you are trying to create a new
proprietary filesystem? That is really a ten year effort, and you would
be much better off to use one of the many existing filesystems. If
the current ones don't meet your exact needs, add the missing
features you need instead of creating a whole new one from scratch.
While I'm a big fan of ext4, there are many other good filesystems out
there - XFS, Btrfs, ZFS, and several flash filesystems.
On Jan 18, 2014, at 5:13, "Lakshmipathi.G" <lakshmipathi g gmail com> wrote: