ecryptfs team mailing list archive

[PowerUser <i-am-sergey@xxxxxxx>]

As for configuration registry:

Filesystems are about files exactly same as sqlite and other databases
are about records. Actually, files could be treated like some sort of
records in some sort of very specific database (if we'll ignore some
specifics).

And we're, the users expect BOTH databases and file systems (at least
these with journal) to care about our data and their integrity. And if
file system does not wants to care about data integrity and rather tries
to push data integrity question into another extra layer like databases
instead of taking care on this question itself, why I should trust to
such file system? Am I really expected to store my valuable data on a
file system which prefers speed over data integrity?

As for me, I want file system to provide data integrity on it's own,
without REQUIRING extra layers like sqlite in applications. If file is
written and closed, it have to be on disk. And as for me, gain of less
fragnemtation and some gain in speed due to temp files in RAM are not
worth of possible data losses due to over-aggressive caching (and ALL
apps will be NEVER rewritten to use extra bloat like sqlite database
just to keep data integrity).

Sorry if some words are offensive or wrong but offer to use sqlite for
data integity REALLY HURTS and RAISES QUESTION: why should I trust my
data to such filesystem? As for now, I'm probably have to stick to ext3
even if this costs some speed but it does not loses data at least.

P.S. I'm also using XFS _but_ only on computers where performance valued
over data integrity and only with UPSes. And I'm unable to supply UPSes
to each and every computer. So - in short, users need RELIABLE file
systems which are providing reliability without extra layers like
sqlite. Please do not disregard this simple fact. Sorry once more if
this sounds offensive or whatever else.

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