Guys,
this is causing data curruption. I'm using Gnome + FC2 and wondering why the act of umounting the drive does not call the "sync" before it's marked as unmounted?
Right now, what I see happening is that, when you click on the Unmount VOlume icon, the icon will straight away gets changed to the unmounted status, but data is only starting to get sync'ed. And I've unknowingly just pulled out the disk before it fully sync's.
This is not good. I think I might have fried a 64MB key not too long ago due to this.
Just because the OS & PC think the card is done moving data around, doesn't mean it is. Flash cards are weird beasts.
On Wed, 01 Sep 2004 09:17:23 +0800, Ow Mun Heng ow.mun.heng@wdc.com wrote:
Guys,
this is causing data curruption. I'm using Gnome + FC2 and wonderingwhy the act of umounting the drive does not call the "sync" before it's marked as unmounted?
Right now, what I see happening is that, when you click on the Unmount VOlume icon, the icon will straight away gets changed to the unmounted status, but data is only starting to get sync'ed. And I've unknowingly just pulled out the disk before it fully sync's.
This is not good. I think I might have fried a 64MB key not too long ago due to this.
-- Ow Mun Heng Fedora GNU/Linux Core 2 on D600 1.4Ghz CPU kernel 2.6.8.1.Aug.29 Neuromancer 01:22:35 up 1 day, 3:41, 2 users, load average: 0.40, 0.54, 0.63
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Ow Mun Heng said:
Guys,
this is causing data curruption. I'm using Gnome + FC2 and wondering why the act of umounting the drive does not call the "sync" before it's marked as unmounted?
Could it be that someone changed the "unmount" in Gnome to actually be an "umount -l"? I have read somewhere that this is the "recommended way of unmounting hot-pluggable storage" but I really can't follow the rational as I believe this will not sync data. I understand that there's an issue with Nautilus (?) accessing the storage and disallowing unmounts, but I believe the fix is rather to re-start Nautilus than to unplug the device without a proper umount...