> You can only fsync given a file descriptor, but I think writing an
fsync binary that opens the file read-only, fsync on the descriptor, and
close the file, should work.
Use this little program to verify your assumptions (I have no time right
now):
#include <fcntl.h> /* open(), O_RDONLY */
#include <unistd.h> /* fsync() */
#include <errno.h> /* errno */
#include <string.h> /* strerror() */
#include <stdio.h> /* fprintf(), stderr */
int
main(int argc, char **argv)
{
char *file_name; /* Name of the file to sync */
int fd; /* File descriptor */
int exit_code=0;
int i;
/* For each argument, except program itself */
for(i=1; i<argc; i++)
{
file_name=argv[i];
/* Open file in readonly mode, unbuffered mode */
fd=open(argv[i], O_RDONLY);
/* Ignore errors */
if(fd==-1)
{
fprintf(stderr,"Cannot open file \"%s\": %s\n",file_name,
strerror(errno));
/* Ignore errors */
exit_code=1; /* Return non-zero exit code to indicate problem. */
continue;
}
if(fsync(fd)==-1)
{
fprintf(stderr,"Cannot open file \"%s\": %s\n",file_name,
strerror(errno));
/* Ignore errors */
exit_code=1; /* Return non-zero exit code to indicate problem. */
continue;
}
}
return exit_code;
}
--
Ext4 data loss
https://bugs.launchpad.net/bugs/317781
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.
Status in “ecryptfs-utils” source package in Ubuntu: Invalid
Status in “linux” source package in Ubuntu: Confirmed
Status in ecryptfs-utils in Ubuntu Jaunty: Invalid
Status in linux in Ubuntu Jaunty: Confirmed
Bug description:
I recently installed Kubuntu Jaunty on a new drive, using Ext4 for all my data.
The first time i had this problem was a few days ago when after a power loss
ktimetracker's config file was replaced by a 0 byte version . No idea if
anything else was affected.. I just noticed ktimetracker right away.
Today, I was experimenting with some BIOS settings that made the system crash
right after loading the desktop. After a clean reboot pretty much any file
written to by any application (during the previous boot) was 0 bytes.
For example Plasma and some of the KDE core config files were reset. Also some
of my MySQL databases were killed...
My EXT4 partitions all use the default settings with no performance tweaks.
Barriers on, extents on, ordered data mode..
I used Ext3 for 2 years and I never had any problems after power losses or
system crashes.
Jaunty has all the recent updates except for the kernel that i don't upgrade
because of bug #315006
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-4-generic 2.6.28-4.6
ProcCmdLine: root=UUID=81942248-db70-46ef-97df-836006aad399 ro rootfstype=ext4
vga=791 all_generic_ide elevator=anticipatory
ProcEnviron:
LANGUAGE=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-4.6-generic
SourcePackage: linux
_______________________________________________
Mailing list: https://launchpad.net/~ecryptfs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ecryptfs
More help : https://help.launchpad.net/ListHelp
