ecryptfs team mailing list archive

[thetrivialstuff <spam@xxxxxxxxxxxxxx>]

Wow, this thing sure is being actively discussed. I might as well weigh
in:

- I side with those that say "lots of small files are a good idea" --
the benefits of having many small human-readable config files are self-
evident to anyone who's ever had to deal with the windows registry.
Suggesting that linux move to a similar approach is... well, I just
can't wrap my head around it. It's crazy. If we take a performance hit
on the filesystem to maintain our small file configs, fine, because if
we try to do something like the windows registry we'll surely suffer the
same (or worse) performance hit later on when it starts to become
cluttered, fragmented, and corrupted.

- I'm guessing that most of the cases described by users here as their
system "locking up" and needing a hard reset were not actually total
lockups. I used to have similar problems with my previous nvidia card --
but really it was only the X server that was locking up (and taking the
keyboard with it). Some have already alluded to the solution -- the
alt+sysrq keyboard combinations. Pressing alt+sysrq+r during an X lockup
will give you keyboard control back* , and then you can use ctrl+alt+f1
to switch to a text console. From there, you can log in and give X a
swift kick in the arse without having to resort to the power button, and
you won't encounter this filesystem problem. (You can also force a full
sync to disk with alt+sysrq+s as I think someone else mentioned.)

*: I don't know why, but in a lot of distros the alt+sysrq stuff is
disabled by default. Google it to figure out how to turn it on, and what
all the other shortcuts are.

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