> > > The CLI command "umount" does this within the Linux / Unix OS. > > That should have the filesystem flush data, but doesn't actually push > out dirty pages for the device — if you accessed it raw at any point > this will not be sufficient. > > (Also, lower layers such as LVM, software RAID, etc, might not flush > their data during the unmount process.) > > > The "sync" command/programming API call is another way to do this > > programmatically. > > That will flush raw blocks from the device also. > > > That is all that is required. > > Those are necessary, but not sufficient, steps, I fear.
so if our raw partitions are up-to-date and the file systems are also, thanks to the 'sync' and 'umount' commands done before device removal, what else are you implying would be necessary before the drive is safely pulled? (obviously I'm referring only to on the hot un-plug side, the hot-plug side obviously involves a different sequence of events, or is that what you're referring to with 'not sufficient'?) -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
