© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hello everyone,
I've had the same problem with Jaunty on 64bit, kernel 2.6.28-8-generic x86_64 and everybody else up to date.
Problem is, as other people here, about first of all the machine locking up completely (still image, mouse freeze too and no hd activity at all) and ext4 data corruption in the form of wiped out (0 byte sized) files (actually as pointed out the ones that were open while it locked or briefly closed before).
The problem manifested itself with a converted ext3 to ext4 partition and also on a newly formatted ext4 partition (both created and used with a pletora of kernel versions, all under jaunty, also counting the latest one).
There's no identified action that triggers the locking up, but it happens quite often, at least once or twice a day (machine is home server, always powered on, with only / and swap on ext4 formatted drive, data are on a RAID5 mdraid XFS formatted set, which never suffered any problem) and seems to be triggered by big files (or directories) transfers (tens of GB) usually when another process actively accesses the disk
eg.:
One of the most common case is while transferring some GB from/to ext4 disk to/from xfs raid set and I try to do a apt-get update and upgrade.
Also happened while downloading Steam games (after a corrupted reg file) in wine (1.1.16) and looking at a HD video, both on ext4 partition.
Disabling trackerd doesn't resolves the problem, yet seems to alleviate it partially by reducing the frequency of the crashes (not too much anyway, let's say 2 to 3 average to 1 to 2 average a day).
Let me know if I can be of any help, I'll be glad to test or provide what I can.
P.S.: By the way, for anyone with apt troubles after a crash during an upgrade for experience this is usually caused by .preinst, .postinst, .prerm and .postrm scripts under /var/lib/dpkg/info, which should be executable script launched before or after installing or removing a given package but get zeroed and are unrecognized. Quick, troubles prone solution is to delete the troublesome script, right solution is to recover the script from another up to date jaunty machine, perfect solution... well you probably have other files zeroed too... ready for a reinstall?