|
I do my best to avoid getting into technical debates with other sysadmins, really. It's a complete waste of time but for some reason I'm living dangerously this morning...
If I had a media client w/ 6TB of storage I'd do whatever it takes to get them off ext3 if for no other reason than the probability they are at or near the folder count limit for the file system.
And, mandatory FSCK is NOT required and can be disabled, especially if you have a nice, replicated SAN or NAS storage system where you can rebuild file system errors while the system is online. Do you seriously believe Enterprise clients on Linux are willing to sit around and wait hours on end for a fsck to complete after a crash>? I spent most of the past decade designing and installing storage solutions for the largest corporations in the World and I've never seen it happen (and no, they were not all proprietary SAN or NAS).
Not to mention the fact that most adult hosting servers are not writing data to the file system that requires such drastic measures, the worst you might see would be corruption in the database which you will quickly find out about and that can be fixed in a few minutes if it occurs. Most adult sites are only writing critical data to the database, everything else is temporary minus the rare occasion when a site edit or encoding session is underway at the time of the crash. Most clients would probably re-do that last task vs. be offline for several hours.
Of course, ditching R1 as your backup solution goes without saying in this scenario. Then again, any client paying me 1k plus per month would be on a load balanced, highly available architecture anyway. It looks like he'll be paying 2k in the near future though and I can't fault any provider for getting some, if you can charge that much for what you give him I envy your sales abilities / incredible luck in getting clients like that.
|