> Let's take a simple example - a database app that does say 30 > transactions/sec. > > In your example, you are extremely likely to lose up to just shy of 5 > seconds of "committed" data - way over 100 transactions! That can be > *really* serious amounts of data and translate into large financial loss. Every database software will do the flushing correctly. > In a second example, let's say you are copying data to disk (say a movie) at > a rate of 50 MB/second. When the power cut hits at just the wrong time, you > will have lost a large chunk of that data that has been "written" to disk > (over 200MB). But why would anyone care about that? I know that the system went down while copying this large movie, so I'll just copy it again. _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
