ecryptfs team mailing list archive

[pablomme <pablomme@xxxxxxxxxxxxxx>]

@Theo: thanks for addressing this point.

> So it's not as simple as "delaying the truncate"; you can delay
committing all operations in the journal, but you can't just delay one
transaction but not another.

I think this is the overall idea people are expressing here, delaying
the entire journal operation stack, not swapping operations.

> However, various disk buffers will get pinned in memory until the
commit takes place, so extending commits may end up chewing up more
memory used by the kernel. TNSTAAFL.

If I understand you correctly, you are implying that delaying the
journal commits is more expensive memory-wise than delaying the data
write? Else I don't understand you concern, the data writes are already
delayed for longer...

Is it possible to exactly synchronize the journal commits and the data
writes (i.e., one immediately after the other)? Would this prevent data
loss for the programs that rely on posixly-unsafe file rewrites?

-- 
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