ecryptfs team mailing list archive

[Theodore Ts'o <tytso@xxxxxxx>]

@Rocko,

If you really want this, you can disable delayed allocation via the
mount option, "nodelalloc".  You will take a performance hit and your
files will be more fragmented.   But if you have applications which
don't call fsync(), and you have an unstable system, then you can use
the mount option.   All I can say is that I don't see these data loss
problems, but everyone has different usage patterns.

In terms of trashed object files in the middle of the build, those
object files are non-precious files.   How often do you crash in the
middle of a build?  Should you slow down all builds just to handle the
rare case where your system crashes in the middle of the build?   Or
would it be better to run "make clean", and rebuild the tree in the case
where you have trashed object files?   It's not like a kernel rebuild
takes that long.  OTOH, if your system is crashing all the time, there's
something else seriously wrong; Linux systems shouldn't be that
unstable.

-- 
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: Fix Released
Status in ecryptfs-utils in Ubuntu Jaunty: Invalid
Status in linux in Ubuntu Jaunty: Fix Released

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