ecryptfs team mailing list archive

[Steffen Neumann <sneumann@xxxxxxxxxxxx>]

Hi,

I found a workaround to the problem of determining the cleartext filenames.
*Before* you delete the zero-byte files, back 'em up:

1) tar find .Private -size 0b | xargs tar -czvf zerofiles.tgz
2) Unmount your encrypted home
3a) Temporarily move the "good" files away:
       mv .Private .Private-real
3b) and restore the "broken" ones:
     tar xzvf zerofiles.tgz
4) remount your encrypted home
    The files will not be usable, but at least you know their names

5a) Unmount your unusable encrypted home
5b) restore the "good" encrypted files:
       mv .Private .Private-broken
       mv .Private-real .Private      

6) Remount and continue.

My last problem: I *still* have 5 files for which I get 
the "Valid eCryptfs headers not found in file header region or xattr region"
error. Since I purged all -size 0b files (verified!) I'd like to know 
how to track those ones down. Is there another find expression
that can nail those down ? Any other debugging option I could/should 
enable to find these 5 files ?

Yours,
Steffen

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