RE: Cook device vs. Raw device

I was under the impression that due to the fact the file was opened with O_SYNC that data integrity was not a concern. definition of O_SYNC - Have each write wait for physicl I/O to complete. (This is not part of POSIX.1 but is supported by SVR4) Will >===== Original Message From "Tyszka, Walt (Walter S)" <wstyszka@ingr.com> ===== >I haven't been following this thread to closely, so pardon me if I am >repeating someone else's observation; but I always thought the most >important difference between raw I/O vs. cooked I/O was data integrity >following a crash. Cooked I/O might report a change as committed, while in >reality the data has only been committed to the disk cache/buffer. With raw >I/O, the data is committed to disk by the engine not the OS. > >Walt ------------------------------------------------------------ This e-mail has been sent to you courtesy of OperaMail, a free web-based service from Opera Software, makers of the award-winning Web Browser - http://www.operasoftware.com ------------------------------------------------------------