FS/Medium checks

[wolfgangw]

This keeps trying to steal itself out the mental back door again and again -- probably because it is such an idiotic issue: Check media/filesystems with DC content for proper hierarchy, filesystem properties explicitly including the dreadful ext2/3 inode size issue etc.

I think whoever insisted that the whole wide DCinema world should keep on having to use 128 bytes for DC media ext2/3 inodes should be taken to a very lonely place for a couple of days :)

Btw, turns out that with Paragon's Ext2/3/4 tools for Mac OS apparently one cannot make a filesystem with 128 byte inodes. Their cli version newfs_ufsd_ExtFS has exactly 2 switches: One for the label, one for allocation block size.

[matmat]

Someone told me that the 128 byte inode requirement comes from the fact that Datasat/Qubeservers running Windows use the Ext2IFS driver (http://www.fs-driver.org/) which only supports 128 byte inode size. I haven't checked if that is actually correct.

[wolfgangw]

Consider systems which are unable to mount contemporary ext2/3 filesystems broken in more than one way. The ISDCF recommendation's particle about 128 bytes-sized inodes needs to go away, I think. What's even more crucial than the item itself is the implied outdatedness of those systems (think security issues).