The drives are mounted read-only, which eliminates the possibility of corruption due to changes being buffered and not written out to disk. The only disk writing that is going on is to the scratch partition - and that is handled raw by the player.

The drives will be fscked when you've made 20 mounts read/write. Prior to the fun with Hijack etc that was pretty much limited to every 20th sync. This parameter can be tweaked, and Hijack has a setting to disable this default checking after 20 r/w mounts. If an operation occurs so that disk might be corrupted, it will still be fscked on next sync. If nothing has visibly gone wrong there is little point in forcing an fsck... just takes a &%¤& long time.

I suspect ext2 and the empeg's method of shutting down must be pretty damn robust.

It is mainly a function of keeping the disks read-only... yanking the player out while a write operations were underway isn't to be recommended

/Michael