ecryptfs team mailing list archive

[3vi1 <launchpad.net@xxxxxxxxxxxxxxx>]

@Theo:

Ahh, that makes sense.  Thanks for the addition info and the time you've
spent on the patches to minimize the impact.

I, and several of the other people here, are probably just feeling more
pain than the average data center ever would see;  A lot of us are
alpha-testing an alpha operating system, and other are running daily
SVNs of Wine with proprietary video drivers.... so crashes and hard
resets aren't really unusual at this point.  :)

Unfortunately for me, they'll probably never be strangers - because I
like to test bleeding edge stuff.  Hopefully your patches make the
truncation less evident for me.  If not, I'll take your suggest and go
back to Ext3 or some other FS that's better suited to what I'm doing.

I think I'll take what I've learned here, do some additional testing,
and suggest that the people working on BOINC change the way they rewrite
their client_state files - because the way they're doing it now makes
both the current *and* the _prev version prone to truncation and hours
of lost work.

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