Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
It's not Transmission's fault. I'm a KDE user (so, I use KTorrent), and I was affected back when this bug was filed (no problems since though). -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
I've yet to see any feedback about the 2.6.31-18 kernel (karmic-proposed) in this critical bug report, and I find that rather strange. The proposed -18-kernel has been out for while now and I count 80+ ext4-fixes in the changelog, including a fix for a data corruption scenario. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/496816 http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.31.8 (upstream stable release from which 2.6.31-18 has patches) https://wiki.ubuntu.com/Testing/EnableProposed -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
Why would the kernel update get corrupted unless the archive or any of the files it contains are several hundred megabytes in size? -- Ryan C. Underwood, neme...@icequake.net -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
On Wed, Jan 27, 2010 at 07:49:06PM -, TragicWarrior wrote: I believe the large file aspect of the bug is an incorrect characterization. If you take a look at comment #184, you will see that I have reproduced the bug on much smaller files. No, you have reproduced some *other* corruption problem that doesn't fit the profile of the original bug report. Please file a separate bug. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
On Wed, Jan 27, 2010 at 08:29:43PM -, TragicWarrior wrote: Why not just re-characterize the bug to match the collected data? Because the data is not related to the bug that was reported, and it's not appropriate to hijack bug reports for unrelated issues. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
@Z149: try Applications-Accessories-Disk Usage Alanyzer, which also can be run from command line as baobab. Push Scan Filesystem button to see where the space goes to. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
Am 2009-12-24 01:17, schrieb Goffi: By the way, I made a cmp of the qtmoko files, I have 2 bytes which differ: Excellent! Scott, could you also post a cmp -l of a corrupted vs a good file? Now, let's have some binary... (Note that cmp -l output is octal) % cmp -l qtmoko-debian-v15.jffs2.clean qtmoko-debian-v15.jffs2.old 16070033 64 164 16070039 257 255 064 = 00110100 164 = 01110100 257 = 1010 255 = 10101101 % cmp -l qtmoko-debian-v15.jffs2.clean qtmoko-debian-v15.jffs2.old2 12701898 0 100 12701904 47 45 000 = 100 = 0100 047 = 00100111 045 = 00100101 You have single bit flips on the second and on the seventh bit. This looks so much like broken memory it virtually has to be broken memory. OTOH, if everybody sees the second and the seventh bit flip then probably ext4 is doing something very stupid. Again, please post your cmp -l results! -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
Goffi, I think your problem is related to the network part. I have a bug report about file corruption using samba: File corruption after copying files via samba from Karmic to Karmic https://bugs.launchpad.net/bugs/491288 Maybe your problem is similar? On Wed, Dec 23, 2009 at 15:26, Goffi go...@goffi.org wrote: I forgot: fsck is OK, and my corrupted files come from network -- 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 direct subscriber of the bug. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
@Goffi: so, all files in which you noticed corruption, come from network? If not Samba, how do you actually get them? Rsync? Torrent? I believe these details could help investigate the problem. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
I tried to reproduce this bug with australia.navit.bin.zip, but I couldn't. # I got the first copy with firefox, and the second with wget wget http://downloads.cloudmade.com/oceania/australia/australia.navit.bin.zip -O ./australia.navit.bin2.zip diff -bq australia.navit.bin.zip australia.navit.bin2.zip md5sum australia.navit.bin* 77fe45bf71779e9263d45b7f31145bbb australia.navit.bin2.zip 77fe45bf71779e9263d45b7f31145bbb australia.navit.bin.zip By the way, if you downloaded that file after 15 December 2009, md5sum should be like above. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
i believe not...some recent updates must have corrected the problem. You guys experiencing any corruption lately? On Sat, Dec 12, 2009 at 7:41 AM, Desh Danz nicol...@libero.it wrote: I'd like to know it too. -- 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 direct subscriber of the bug. Status in The Linux Kernel: New Status in Ubuntu Release Notes: Fix Released Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Karmic: Triaged 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: USERPID ACCESS COMMAND /dev/snd/controlC0: vorlon 3350 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xee24 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 To unsubscribe from this bug, go to: https://bugs.launchpad.net/linux/+bug/453579/+subscribe -- ÐÌĞ -- http://www.everythinglegit.com http://twitter.com/ram130 http://www.myspace.com/everythinglegit -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
I have not installed those packages, and I really doubt Scott has either since I think he maintains them. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
i just installed karmic on a 1TB sataand my flash drive 16GB...lets see how it goes! both EXT4..if it lets me down, then yall got sum serious problems.. On Wed, Nov 18, 2009 at 1:13 AM, Nicky Gillette nickygille...@gmail.comwrote: I meant that it happens with or without encryption on 9.10 in the comment above, if it was unclear. -- 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 direct subscriber of the bug. Status in The Linux Kernel: New Status in Ubuntu Release Notes: Fix Released Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Karmic: Triaged 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: USERPID ACCESS COMMAND /dev/snd/controlC0: vorlon 3350 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xee24 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 -- ÐÌĞ -- http://www.goeazy.com http://twitter.com/ram130 http://www.myspace.com/everythinglegit -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
and yes i am doing large transfers of files over 16GBhow do you check the checksums? On Wed, Nov 18, 2009 at 2:50 AM, Ram'on McNally ram...@gmail.com wrote: i just installed karmic on a 1TB sataand my flash drive 16GB...lets see how it goes! both EXT4..if it lets me down, then yall got sum serious problems.. On Wed, Nov 18, 2009 at 1:13 AM, Nicky Gillette nickygille...@gmail.comwrote: I meant that it happens with or without encryption on 9.10 in the comment above, if it was unclear. -- 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 direct subscriber of the bug. Status in The Linux Kernel: New Status in Ubuntu Release Notes: Fix Released Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Karmic: Triaged 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: USERPID ACCESS COMMAND /dev/snd/controlC0: vorlon 3350 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xee24 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 -- ÐÌĞ -- http://www.goeazy.com http://twitter.com/ram130 http://www.myspace.com/everythinglegit -- ÐÌĞ -- http://www.goeazy.com http://twitter.com/ram130 http://www.myspace.com/everythinglegit -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
That's what I had use to know I got a bad sector in the first place. I tried runing the short test and the other one that wasn't extended. All failed before they could complete bout 90%. Tried just awhile ago and it failed to continue runing after 10sec, saying cannot read. I jus ran a memtest, its clean. Windows 7 finally booted, but saying it cannot access my desktop and a lot of errors now, sumting about read error and corrupted files. Its just problem after problem. I guess everyone else here is better off than me right now? On Nov 12, 2009 3:20 AM, unggnu ung...@googlemail.com wrote: The tool to check S.M.A.R.T in Karmic is called Disk Utility (gnome- disk-utility) and it is also possible before with the smartmontools. -- in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on... -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
Wow now that's a test!!! I think karmic corrupted my windows7 and two data partitions. I installed karmic on a brand new 21days old 500GB hard drive. Been transfering files for 2 weeks from my failing 320GB. After that was done I tried booting back into windows7, failed. Karmic crashes occasionally for no reason!! Decided to run start up repair, no problems then I ran chkdsk, all of corrupted files on each partition! ..to top it off disk utility is reporting my hard drive now has a bad sector!! Sumone help me before I go insane On Nov 11, 2009 9:26 PM, Andrew M. 2bitoperati...@gmail.com wrote: oh yes, one more thing, all fs's were created formatted by the Karmic installer, using the release media -- in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on... -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
Er...this is only for ext4. Win7 does not run on ext4. Sounds like that bad sector is to blame. Just because it's new doesn't mean it's not broken. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
I used Karmic to create the partitions, 2 NTFS, SWAP an EXT4. The bad sector didn't show up until I was doing copying files...so far it says One bad sector. It just seems ironic this corruption problem is here then this happens. On Thu, Nov 12, 2009 at 1:39 AM, Mackenzie Morgan maco...@gmail.com wrote: Er...this is only for ext4. Win7 does not run on ext4. Sounds like that bad sector is to blame. Just because it's new doesn't mean it's not broken. -- 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 direct subscriber of the bug. Status in The Linux Kernel: New Status in Ubuntu Release Notes: Fix Released Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Karmic: Triaged 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: USERPID ACCESS COMMAND /dev/snd/controlC0: vorlon 3350 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xee24 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 -- ÐÌĞ -- http://www.goeazy.com http://twitter.com/ram130 http://www.myspace.com/everythinglegit -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
