mythbuntu-bugs team mailing list archive

[Scott James Remnant <scott@xxxxxxxxxxxxx>]

I'm going to mark this bug as Invalid (I'm the original reporter)

I've not been able to replicate it on production hardware, and not been
able to replicate it on the hardware where I was originally able to
replicate it with karmic as it existed at release time.

Therefore I can only conclude that the problem was with faulty hardware,
exasperated by a kernel issue that was fixed before karmic was released.

If you are a user still experiencing problems with the ext4 (or any
other) filesystem, including those resulting in fsck errors, then you
don't have the same bug that I reported so should report a new bug.
Don't open this one unless you've snuck into my house and stolen my
laptop <g>

** Changed in: linux (Ubuntu)
       Status: Triaged => Invalid

** Changed in: linux (Ubuntu Karmic)
       Status: Triaged => Invalid

** Changed in: linux
       Status: New => Invalid

-- 
in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is a direct subscriber.

Status in The Linux Kernel: Invalid
Status in Ubuntu Release Notes: Fix Released
Status in “linux” package in Ubuntu: Invalid
Status in “linux” source package in Karmic: Invalid

Bug description:
There are worrying reports of filesystem corruption on ext4 in karmic.  Scott says:

12:36 < Keybuk> this whole ext4 thing is worrying me
12:36 < Keybuk> I just downloaded an iso image, md5sum didn't match
12:36 < Keybuk> downloaded it into an ext3 partition, matched just fine
12:59 < Keybuk> and I know mvo has seen bugs with corrupted .debs in /var/cache/apt/archives
12:59 < Keybuk> which seems to imply its any file large enough to use lots of extents

I'm opening this bug report so that this bug gets tracked & triaged for karmic.  If we're unable to isolate the issue, we should consider rolling back to ext3 as the default filesystem in the installer.

ProblemType: Bug
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  vorlon     3350 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xee240000 irq 17'
   Mixer name	: 'Analog Devices AD1981'
   Components	: 'HDA:11d41981,17aa2025,00100200'
   Controls      : 20
   Simple ctrls  : 11
Date: Fri Oct 16 16:01:26 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=f108133c-6b9d-4d28-9058-0b3a0c5549b4
MachineType: LENOVO 6371CTO
Package: linux-image-2.6.31-14-generic 2.6.31-14.46
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=/dev/mapper/hostname-root ro
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
RelatedPackageVersions: linux-firmware 1.22
SourcePackage: linux
Uname: Linux 2.6.31-13-generic x86_64
WpaSupplicantLog:

dmi.bios.date: 12/27/2006
dmi.bios.vendor: LENOVO
dmi.bios.version: 7IET23WW (1.04 )
dmi.board.name: 6371CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7IET23WW(1.04):bd12/27/2006:svnLENOVO:pn6371CTO:pvrThinkPadT60:rvnLENOVO:rn6371CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 6371CTO
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO

ls