| |||||||||||||
Ext4 data corruption trouble [Updated]Ext4 data corruption trouble [Updated]Posted Oct 25, 2012 16:02 UTC (Thu) by wahern (subscriber, #37304)In reply to: Ext4 data corruption trouble [Updated] by butlerm Parent article: Ext4 data corruption trouble [Updated]
I still have an ingrained habit of typing `sync' at idle moments in my shell, picked up in the early days of ext2. Re-downloading the Slackware floppy set (because invariably one of the disks of a previous downloaded set would be go bad) over a 2400 baud modem was not fun times. Because things were generally less stable back then, and you never knew when the system might crash and leave the disk corrupt and unbootable, vigorous and frequent syncing was the only alternative.
(Log in to post comments)
Ext4 data corruption trouble [Updated] Posted Oct 26, 2012 0:44 UTC (Fri) by jhardin (guest, #3297) [Link] I still have an ingrained habit of typing `sync' at idle moments in my shell, picked up in the early days of ext2.+1, except I picked up the habit on SCO Xenix. sync;sync;sync
Ext4 data corruption trouble [Updated] Posted Oct 26, 2012 1:22 UTC (Fri) by pr1268 (subscriber, #24648) [Link] I like this solution:
/* 3sync.c */
#include <unistd.h> /* for sync(2) */
#include <time.h> /* for struct timespec and nanosleep(2) */
int main()
{
struct timespec ts = { 0, 1000000L };
sync();
(void) nanosleep(&ts, 0);
sync();
(void) nanosleep(&ts, 0);
sync();
return 0;
}
Compiled and placed in $HOME/bin (which is in $PATH), and now it gets used quite frequently in other scripts I run. Which either (1) is horribly inefficient, and/or (2) shows how paranoid I am with data corruption. Sigh.
|
|||||||||||||