Bill Eldridge wrote: ... > While I simply don't know with accuracy, this sounds like FUD on the > part of Linux fans. > NTFS is used on millions of mission critical machines, not to sound like > a marketing message, > and if you got errors every time there was a quick boot/power outage > (i.e. these accumulated > errors left over and not burned to disk), I can't imagine anyone using > NTFS or even Windows.
Dunno. I was just reporting the reason supplied by the person responsible. I suspect the errors are small but cumulative, which would allow for corrections as long as the next shutdown was normal. Thus, it may take a lot of fast boot/power outage executions in a row for the error correction to not catch up. As for mission critical Windows boxen, I'm mostly familiar with NTFS used in mission critical control systems, where it does not get rebooted very often, now that the 45 day issue is resolved. I'm not sure it's safe to say there are millions of mission critical machines running Windows - there certainly are millions of Windows machines, but most of them are not mission critical. > Also, I can't imagine NTFS being around for 11 years with various > upgrades and having this error > situation persist. My experience is that NTFS is more stable than it used to be. I can remember early versions of NT 4.0 eating itself - literally overwriting chunks of the winnt directory/folder. I haven't had that happen in a long while. -- Ray Parks [EMAIL PROTECTED] IDART Project Lead Voice:505-844-4024 IORTA Department Mobile:505-238-9359 http://www.sandia.gov/scada Fax:505-844-9641 http://www.sandia.gov/idart Pager:800-690-5288 ============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College lectures, archives, unsubscribe, maps at http://www.friam.org
