Linux – How to find what filesystem is on a logical volume

Excellent article about flash filesystems.

Important question when talking about flash filesystems is following: What is wear leveling? Wikipedia article. Basically, on flash disks you can write limited number of times until block goes bad. After that, filesystem (if there is no built-in wear leveling management on hardware, as in case of SSDs there usually is) must mark that block as invalid, and avoid using it anymore.

Typical filesystems (for example ReiserFS, NTFS, ext3 and so on) are designed for hard disks, that do not have such limitations.

JFFS2

Includes compression and elegant wear leveling protection.

YAFFS2

• Single thing that makes the difference: short mount times, after successful umount.
• Implements write once property: once data is written to one block, there is no need to rewrite it. This is important, as it reduces wear.

LogFS

• Not very mature, but already included in Linux kernel tree.
• Supports larger filesystems than JFFS2/YAFFS2 without problems.

UBIFS

• More mature than LogFS
• Write caching support
• On scalability: article. On large disks, better performance than with JFFS2

ext4

If no driver or card (for example SSD drives do have internal wear leveling, at least usually) handle wear leveling, then ext4 is not the best idea, as it is not intended for raw flash usage.

Which one is the best?

Of course, it depends on usage and support. From what I read on the Internet, I would recommend UBIFS. Good support for large filesystems, mature development phase, adequate performance and no huge downsides.

You still looking for help on this? One way you might find affected files is to tar the filesystem to /dev/null. Any file containing an error will be complained about by tar. Something like:

tar cf /dev/null /file/system/to/check

might do it for you.