Well AFAIK the plug won't boot into fsck at all (maybe since the boot is being rerouted from the nand?) and therefore cannot check itself. At least it never worked for me and some threads have made mention that fsck won't execute. So to be safe, before the plug booted again I connected the drive to a linux machine and ran the fsck.ext4 from there.
It isn't "necessary" but should any errors occur and you believe it could be solved with a harddrive check, then do it. I had a couple of brown-outs that knocked off the power to the plug but it booted back with zero problem. That's why when I ran the fsck I didn't get any warnings or errors

. The time I had to restore was due to me being a little reckless with my root dir, not the power outage.
My two cents: use ext3/4 for the security of the journal. Should something go wrong, fsck it. But chances are it will come back with no problems. I just added the backup to cron.weekly for peace-of-mind. But if booting from a flash keep it ext2 to lower the number of I/Os.
Pogoplug Pro w/ Wireless User -> decomm.Cubox-i4pro User4TB eSATA HDD (8g/3700+ Sw/Storage)
Kodi / Transmission / Minidlna / Samba / Batch-audio-conversions / Lighttpd
------------------------------
Rollback Machine - Thanks to
impatt