Originally Posted by jkozee
Can you provide details on the additional alignment being done on the inodes. If they are 512 bytes, wouldn't they fall on a 4k boundary if the partition started on one?
Each inode is 512 bytes and it's followed immediately by a backup copy, so that's 1024 bytes each.
Multiple factors come into play here, so skip the rest of this if tech stuff bores you.
There are 3 types of "zones". File zones are used for a fairly standard file system with directories etc. Inode zones hold the inodes, which tell you where to look on the disk for a particular file or media stream. Media zones hold the actual recordings.
The headers for all 3 types of zones and the actual file and inode zones are located in the MFS application partitions. If you align the MFS media partitions correctly for a 4KB sector drive (and they do on Roamios) that takes care of one problem, but aligning the MFS application partitions doesn't automatically align the file and inode zones within them for 4K drives. In fact it never
does on the factory layout.
What I did in mfsr was to make sure that the file and inode zones start at 4K boundaries. Doing that wastes a few 512 byte 'sectors' here and there, but I got that back and more by laying out the media partitions more efficiently.
Here's where somebody will probably say that since each inode takes up 1024 bytes, aligning the start of the zone doesn't matter. Did I mention that the minimum read/write block size in the inode zones is 256MB?