ecryptfs team mailing list archive

[Danny Daemonic <DannyDaemonic@xxxxxxxxx>]

If POSIX is undefined in this regard then we should also be opening bug
reports with the developers who have this problem.

I see people here complaining about GNOME, I looked through their bugs
and couldn't find any one reporting this.  For people who would want to
run with the special ext4 mount option that would speed up their system,
it might be a good idea to open a bug.

Following that train of thought, Theo says KDE has the same problem,
although no one here has mentioned it.  I use KDE and if this is a
design flaw I'd like it fixed so ext4 can be mounted with the faster
mount option.  I searched through the KDE bugs and only found people
complaining that KDE fdatasyncs too often (preventing their laptop hard
drive from spinning down).  I also ran across closed reports of people
saying it fsyncs too often.  Has anyone seen the 0 byte truncation issue
with KDE, or is Theo just assuming since GNOME does it, KDE must also?

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