ecryptfs team mailing list archive

[Chris Schanck <chris@xxxxxxxxxxx>]

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

This, to me gets to the root of the loggerheads displayed in this bug.
The reason Ubuntu is different is because it is *more* likely (I
suspect) to be deployed as a personal use desktop. Since it gets thrown
onto any number of laptops and such, it is used with a large array of
relatively new hardware (I am on a Dell d830 right now -- about a year
old). Binary drivers? Fact of life. Without the nvidia driver I'd not
use Linux. Sorry, the user experience matters.

This use model conflicts with the "no binary drivers" ivory tower
mentality. Sorry, but under windows this stuff just works. If you accept
that Linux is a serious desktop os, you'll have to live with the reality
of binary drivers, lousy programmers, etc. While ext4 has some wonderful
performance and behavior, and came claim to being "correct" as far as
POSIX goes, it's a bit much to be a spec lawyer when usage models that
work cease to do so.

I understand your point, and even agree that it is an app error by the
spec. But this puts users in the situation of having their machines fail
where they didn't use to. As soon as they move to ext4. Accurate
explanations won't change that impression.

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