ecryptfs team mailing list archive

[pablomme <pablomme@xxxxxxxxxxxxxx>]

@Theo: could you comment on the points made above (e.g., comment #98),
namely about why the truncate operation is immediate and the writing
operation is delayed? I think that's a very good point; if both
operations were delayed no (old) data would be lost, while achieving top
performance.

> Finally, I'll note that Fedora folks haven't really been complaining
about this, so far as I know. Which should make people ask the question,
"why is Ubuntu different"?

Well:
- Release cycle timing: alpha 1 for Ubuntu Jaunty was released last November, while the alpha for Fedora 11 was released in February. Fedora 11 will have ext4 by default, I'm pretty sure there _will_ be complaints if they don't address this problem, just give it time.
- Feature list: Fedora 11 is including experimental btrfs support. The truly adventurous will be trying that. The not-so-adventurous may as well wait for the beta to try fedora 11 out.
- Number of users: the more distribution users there are, the more comments and complaints you'll get for a given problem. I've no data to back this up, but in my perception Ubuntu does have more users than Fedora.

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