ecryptfs team mailing list archive

[Theodore Ts'o <tytso@xxxxxxx>]

Jose, please open a separate bug, as this is an entirely different
problem.   (I really hate Ubuntu bugs that have a generic description,
because it seems to generate "Ubuntu Launchpad Syndrome" --- a problem
which seems to cause users to search for bugs, see something that looks
vaguely similar, and then they add a "me too" to a bug, instead of
opening a new bug.)

Launchpad simply doesn't scale, and it's painful as all heck to deal
with a bug with 200 comments.  And this is entirely unrelated to the
problem that people were dealing with --- and which has been solved in
the Ubuntu kernels and in 2.6.29.

The errors you are reporting are entirely consistent with this which I
found earlier in your dmesg:

[    7.531490] EXT4-fs warning: mounting fs with errors, running e2fsck
is recommended

I'm guessing you didn't set up your /etc/fstab correctly so that the
filesystem on your /dev/mmcblk0p1 (i.e., your SD card) would have e2fsck
run on reboot when it had errors.  That would certainly be consistent
with the dmesg log which you showed.

As for what caused the problem, I'm not entirely sure.   One things is
for sure, though --- you need to fix up your filesystem first, and I
would recommend that you check out your /etc/fstab to make sure that the
filesystem is checked at boot-up if it needs it.   That means the fsck
pass field of /etc/fstab needs to be non-zero.  In any case, please open
a new bug, and put a pointer in this launchpad bug to the new bug so
people who are interested can follow you to the new bug.  Thanks!

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