ecryptfs team mailing list archive

["Tom B." <spam@xxxxxxxxx>]

@Volodymyr

I finished recompiling the kernel with Theodore Ts'o patches, and reran
Volodymyr's test cases with the patched kernel.  The results are:

File System Method Performance (Typical, Minimum, Maximum) #Lost %Lost

ext4patch	1	0.44	0.41	0.50	1	1.00%
ext4patch	2	0.32	0.32	0.40	0	0.00%
ext4patch	3	0.20	0.18	0.20	0	0.00%
ext4patch	4	0.25	0.25	0.25	0	0.00%
ext4patch	5	0.26	0.26	0.33	0	0.00%
ext4patch	6	0.41	0.33	0.42	0	0.00%

Essentially, the patches work.  Ext4, with the patch, has the same data
loss as the ext3 file system.

Adding fsync() to the code results in a significant decrease in loop
speed.  As such, for the application writers, only add fsync() to your
code when you want to be really sure the data has been written to disk,
like when you are writing a database.

** Attachment added: "Benchmarks in OpenOffice V2"
   http://launchpadlibrarian.net/23897042/Ext3Ext4BenchmarksV2.ods

-- 
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: Fix Released
Status in ecryptfs-utils in Ubuntu Jaunty: Invalid
Status in linux in Ubuntu Jaunty: Fix Released

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