← Back to team overview

ecryptfs team mailing list archive

[Bug 317781] Re: Ext4 data loss

 

I am experiencing the exact same problem... I was with an ext3 converted to ext4 partition and ended up reinstalling everything as data loss killed all /etc...
My fresh Jaunty on a fresh ext4 already gave me twice 'read-only file system' and now I don't know what to do...

   Olli Salonen wrote on 2009-03-07: (permalink)

   I'm experiencing something similar, but with a twist.

   After few hours to two days of use, my ext4 /home partition becomes
read-only all of a sudden. I usually close my session, unmount  home,
run fsck on the partition, and remount. Occasionally it leads to data
loss, depending on what I was doing.

   I'm currently on 2.6.28-6 because the last upgrade attempt lead to an
unbootable system (also running ext4 on root partition), so I don't know
if this is a fixed issue.


Sorry if someone gave a solution already, this bug is getting too long and I didn't find it... I am not new on linux, I am used to broken system by myself but here I don't get what is going on and I don't wanna start it without an idea to repair...
please help!

Thanks

I am sorry if

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