On Thu, 2009-10-29 at 14:57 +, Bob McElrath wrote:
I have seen problems like this with large files on multiple fs's and
ultimately it was a RAM problem. Scott, can you run memtester and/or
memtest86 at bootup to verify that you don't have bad RAM? Is your CPU
overclocked? CPU errors
On Thu, 2009-10-29 at 18:33 +, Martin Pitt wrote:
Lemmiwinks [2009-10-29 18:02 -]:
Forgot to mention, that I've got actually an Ext3 file system, which I
updated to Ext4 soon after Jaunty was released, with no problems at all.
Scott, did you also upgrade your's to ext4, or was
No, this is not upstream bug #14354. There is no overlap between the
described problems.
** Changed in: linux
Importance: Unknown = Undecided
** Changed in: linux
Status: Unknown = New
** Changed in: linux
Remote watch: Linux Kernel Bug Tracker #14354 = None
** Summary changed:
-
I haven't downloaded anymore large files since then on the basis that it'd be a
waste of bandwidth
On Saturday 07 November 2009 4:12:05 pm Ramon wrote:
yea thats true. Have you experience any more corruption since?
On Sat, Nov 7, 2009 at 3:20 PM, Mackenzie Morgan maco...@gmail.com
wrote:
Looks like the is mostly solved upstream by reverting patch
d0646f7b636d067d715fab52a2ba9c6f0f46b0d7 and adding the patch
487caeef9fc08c0565e082c40a8aaf58dad92bbb.
@apw could you or csurbhi build a test kernel and post here so folks can
test?
Thanks
~pete
** Changed in: linux
Importance:
I restarted my system the hard way and it would not boot. So i checked it
from another install with fsck and it found some errors. I'm beginning to
worry about a possible future corruption. What is the status of this
problem?
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
Ramon:
That's not what this bug is about. Improperly rebooting runs the risk
of breaking your system on *any* filesystem. This bug is about
*individual files* which are very large becoming corrupt and NOT
having any effect on fsck.
--
corruption of large files reported with linux 2.6.31-14.46
yea thats true. Have you experience any more corruption since?
On Sat, Nov 7, 2009 at 3:20 PM, Mackenzie Morgan maco...@gmail.com
wrote:
Ramon:
That's not what this bug is about. Improperly rebooting runs the risk
of breaking your system on *any* filesystem. This bug is about
*individual
Is this bug related somewhat to the following:
http://bugzilla.kernel.org/show_bug.cgi?id=14385
http://marc.info/?l=linux-kernelm=125504643703877w=4
?
** Bug watch added: Linux Kernel Bug Tracker #14385
http://bugzilla.kernel.org/show_bug.cgi?id=14385
--
corruption of large files reported
Hello.
I have wrote a C program to implement the test I described above. Currently, it
checks 100x 8K blocks around the 512MB mark, by swapping them with each other,
back to front. Running the program twice should thus result in an identical
file. Using this program, you can check that
I have a freshly installed ubuntu 9.10 with 2 newly created ext4
partitions (45GiB for / and 870GiB for /home). I did not encounter any
problem so far. (The /home drive contains ~500GiB of films) Also the
tester program of comment #112 doesn't reveal any problems. So I'm lucky
for now and will
Furthermore, I should state the full kernel version that the final
version of Ubuntu (which we did our testing on) is 2.6.31-14.48 and not
14-46. Is there a fix from 46 to 48?
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You
On Tue, Nov 03, 2009 at 11:01:04AM -, Starcraftmazter wrote:
Furthermore, I should state the full kernel version that the final
version of Ubuntu (which we did our testing on) is 2.6.31-14.48 and not
14-46. Is there a fix from 46 to 48?
No. The bug title reflects the version of the kernel
@Steve Langasek
I understand that, though what I'm wondering is whether there was any change
from 46 to 48, which could have fixed this issue.
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You received this bug notification because
I had -14.48 when I hit it.
--
corruption of large files 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
I have a fresh installation of Karmic Koala, and I've already have two times
corrupted fs.
Ubuntu does not boot and complain about fs it cannot mount.
I have to do fsck in order to repair the things.
But the perl script above (of Starcraftmazter) said that hashes are
equal.
--
corruption of
Is this not fixed via
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/317781 ?
If so, will the iso images for Karmic be updated anytime soon, or will
this only be available post-install?
Maybe off base, sorry if so.
--
corruption of large files reported with linux 2.6.31-14.46 on
I guess it would help if I pasted the right link... Please ignore the
previous link.
http://bugzilla.kernel.org/show_bug.cgi?id=14354
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You received this bug notification because you are
Well I am not sure but heres a copy of what mine said after a clean
install Linux 2.6.31-14-generic-pae ...also I have not really notice
any corruption except couple hours ago when i tried to reinstall grub2 i
got a segmentation fault error.
--
corruption of large files reported with linux
This might be a stupid question, but Karmic does ship with the Kernel
2.6.31-14.48 and not 14.46 right? Can anybody elaborate?
I did a fresh install with newly created ext4 partitions and have not
yet encountered anything. Well I didnt really try to produce an error
since this is my production
** Changed in: linux
Importance: Unknown = Undecided
** Changed in: linux
Status: Confirmed = New
** Changed in: linux
Remote watch: Linux Kernel Bug Tracker #14354 = None
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
@ Kai Blin,
it should be made clear that testing with an external USB drive is not at all a
reliable test. I've got through _several_ USB drives that systematically
corrupted large files regardless to the HardDisk, filesystem and host computer
used. This happens especially with large capacity
@aldebx
Dunno, connecting all of my drives to all of my other boxes, I don't see any
issues like that. However, I think I've already identified the system used as
the real cause of my particular issue.
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
Did everyone affected do a memtest like the suggestion earlier
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/453579/comments/88)
I have had the EXACT same symptoms ('cept it was a 4.7 GB ISO), on ext3
and it was a SINGLE bad line in memtest. So please run memtest Scott.
Or anyone else
@aldebx
Of course I realise this, perhaps I need to elaborate my idea. I mean,
since the error apparently occurs when large files are edited, a test
should be devised whereby changes are made to a large file, saved, and
then un-done and saved - and the before and after checksums compared, to
see
I also had this issue but I can't really nail it down. The explanation
that it has only something to do with Kernel 2.6.32-rc* makes sense. I
used it several times on my two systems. I got different md5 for the
same file and if I played a video which was affected the player stops
and the hard
I think Steve was right at post #84: the link to the linux kernel bug
should be dropped, as all of the circumstances of this bug are different
from the one in the link. How did this upstream link get re-
established?
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
** Changed in: linux
Status: Unknown = Confirmed
--
corruption of large files 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
OK, the bug is in kernel 2.6.32. Kosmic, er, Karmic Koala is 2.6.31. No
wonder I wasn't able to reproduce it.
http://bugzilla.kernel.org/show_bug.cgi?id=14354
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You received this bug
@Kai Blin: Can you please confirm the kernel version this was happening
with?
--
corruption of large files 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.
I'm seeing this on 2.6.31.4 of the beagleboard armel kernel from Launchpad.
However, this might be a false alarm on my side, pointing at a hardware issue
instead. I've reformatted the partition to ext3 and I'm still seeing similar
effects. This is an external USB drive, which might be one part
** Changed in: linux
Importance: Undecided = Unknown
** Changed in: linux
Status: New = Unknown
** Changed in: linux
Remote watch: None = Linux Kernel Bug Tracker #14354
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You
** Changed in: linux
Importance: Unknown = Undecided
** Changed in: linux
Status: Unknown = New
** Changed in: linux
Remote watch: Linux Kernel Bug Tracker #14354 = None
** Changed in: linux
Importance: Undecided = Unknown
** Changed in: linux
Status: New = Unknown
**
http://lkml.org/lkml/2009/3/24/415
--
corruption of large files 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
I am confused about this bug. All comments speak about freshly-created
ext4 filesystems, as well as the Karmic Release Notes. But what about
already-present filesystems? Right now my / is ext3 and /home is ext4 on
Jaunty. If I do a dist-upgrade to Karmic, will I be affected? What about
converting
We don't know the cause, so that's hard to answer. So far it seems that ext3
-- ext4 conversions are safe. Kind of makes sense, since the on-disk system
is a bit different. As to whether created-by-Karmic or in-use-by-Karmic is
the trouble here, we don't know yet. I think only 3 people so
I tried to reproduce this on my Latitude D630 with an intel x25-m, 9.10
fresh format/install mounted raw, and was unable to.
Immediately after grabbing ubuntu-9.10-desktop-amd64.iso, the md5sum was
dc51c1d7e3e173dcab4e0b9ad2be2bbf, and did not change even after a
reboot.
--
corruption of large
fimbulvetr - did you try editing the file?
On that note, I'm doing a fresh install of 9.10 with ext4 on my laptop
around the start of next week, and I'm wondering if anyone can suggest
some methods to try and reproduce the bug. So far I'm thinking about
obtaining a very large file, copying it
Thanks so much for working on this critical issue. I wait to install
Karmic till it is fixed, so please hurry up :-) As I often have large
files (around 1 GB).
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You received this bug
Documented at
https://wiki.ubuntu.com/KarmicKoala/ReleaseNotes#Possible%20corruption%20of%20large%20files%20with%20ext4%20filesystem:
There have been some reports of data corruption with fresh (not
upgraded) ext4 file systems using the Ubuntu 9.10 kernel when writing to
large files (over 512MB).
Steve, I can confirm that in my setup.
Test is easy, as described by Scott.
I've copied over the first iso I found on my PC to my fileserver running
an ext4 /data partition. Then I had some fun with md5sum:
k...@woodstock:/data/iso$ md5sum en_win_xp_pro_n.iso
138468d380b84e6b9e9a8648efb97143
Oh, I forgot to mention that d11a45c61466f2b22757e0e449e2fe90 is not the
correct checksum the file is supposed to have.
--
corruption of large files 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
I have seen problems like this with large files on multiple fs's and
ultimately it was a RAM problem. Scott, can you run memtester and/or
memtest86 at bootup to verify that you don't have bad RAM? Is your CPU
overclocked? CPU errors can also be detected with burn* programs
(cpuburn package). A
A few days ago, a video file in my home folder, which was over 300MB large,
became unusable. Nautilus says the file has 0 bytes. When I try to open it,
every player reports, that the stream does not contain any data.
Unfortunately I can not tell when exactly or what the file corruption caused.
Forgot to mention, that I've got actually an Ext3 file system, which I
updated to Ext4 soon after Jaunty was released, with no problems at all.
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You received this bug notification because
Lemmiwinks [2009-10-29 18:02 -]:
Forgot to mention, that I've got actually an Ext3 file system, which I
updated to Ext4 soon after Jaunty was released, with no problems at all.
Scott, did you also upgrade your's to ext4, or was that a clean
mkfs.ext4?
--
corruption of large files reported
I have an ext4 fs that I created in jaunty as a fresh ext4 fs (during
the jaunty beta cycle).
The fs is on lvm and is close to 1 TB in size...it's 92% full with mp4
files in frequent use, and I have not yet seen this issue.
I upgraded this machine to karmic just over a week ago.
--
corruption
Lemmiwinks: Sounds more like the old 0-byte bug that was in Jaunty's
ext4. Scott's bug keeps the files the same size.
I'm getting this too with the .isos I downloaded today. Mine is not a
ext3 -- ext4 conversion. It was formatted as ext4 by the Karmic alpha 3
or 4 installer. Unlike Scott and
I just finished a clean install of 9.10 (new default
partitions...nothing retained from previous install) on a Toshiba
notebook with an old-school 120 GB parallel ATA drive (whatever you call
the drives that came before SATA) and 2 GB of RAM.
I ran the following commands:
openssl rand -out foo
Neumarke,
The relation to that upstream bug is tenuous at best. The upstream bug:
- is reported against a newer kernel than the one we're shipping
- is reported to only happen when ext4 is on top of the DM layer, whereas
Scott's case was ext4 on a raw device
- is reported in connection with an
Since it seems the fix has been planned for karmic-updates, should we expect
ext3 to be used as the default fs when installing Karmic?
I'm quite worried about the impact this bug could have on new users migrating
to Ubuntu.
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
Setting the milestone does not mean that a fix is planned for karmic-
updates. So far, it doesn't appear that Scott's original problem is
reproducible for anyone else. We will stay on this bug to try to
confirm it and find a fix, but we aren't going to change the default fs
for a bug that only
@mabovo: a regular fat32 filesystem only supports files up to about 4GB,
wich explains your problem.
I haven't expirienced this on ext4 yet, but I did notice some corruption on
ext3 a while back, nothing important, but it could have been corruptions
introduced with the transfer of the file. I
You can add me as a second user seeing the problem. My original report
is here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/459839
I've seen the bug with two independent installations to ext4. In my
case, a fsck does seem to repair the problem, making a non-bootable
system bootable
I've seen the bug with two independent installations to ext4. In my
case, a fsck does seem to repair the problem, making a non-bootable
system bootable again. The occurrence of disk errors is sporadic.
That doesn't sound at all like the bug Scott has described.
--
corruption of large files
Proposed release note:
There have been some reports of data corruption with fresh (not
upgraded) ext4 file systems with large files (over 512MB). The issue
is under investigation. Users who routinely manipulate large files may
want to consider using ext3 file systems until this issue is
On the issue how many people are seeing this problem, and I hope I'm not
misunderstanding the relationships between bugs here:
This bug is assigned to linux-kernel-bugs #14354 in which Linus Torvalds
himself claims to be seeing filesystem corruption, starting here:
** Changed in: linux (Ubuntu Karmic)
Milestone: ubuntu-9.10 = karmic-updates
--
corruption of large files 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.
On Wed, 2009-10-21 at 20:07 +, John Johansen wrote:
Since I haven't reproduced this error yet I would like to get a better
handle on what people are seeing here. Is it file system corruption
(errors that show up in fsck), or file corruption where fsck does not
report any errors. Also
I'm a litte worried about this one too, so I gave testing it a shot.
Created a ~20GiB ext4 filesystem and copied a 1.2GiB file there.
Compared with md5sum and the checksum was the same. Running Karmic RC
with 2.6.31-14.
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=14354
Importance: Unknown
Status: Unknown
--
corruption of large files 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
Sory if I hijack this bug but seems that there is something related if I am not
totally wrong:
I am using 9.10 with Mac2,1, ext4 on sda3.
When trying to copy a DVD like Snow or Leopard.iso (aprox. 7.5 GB) into an
external HD *fat32), Nautilus stop the process in the middle displaying an
error
mabovo, your issue is completely unrelated.
--
corruption of large files 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
Just to confirm, is this just an issue with 2.6.31-14.46 kernel or is it
also with the 2.6.31-14.48 kernel?
--
corruption of large files 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,
The code path that is being patched in the ext4_write_inode() function
is new to 2.6.32 and does not exist in Karmic.
It may be possible (though unlikely), that the read only non-journaled
case calling ext4_force_commit is causing the corruption as in the
2.6.32 patch this case is short
Since I haven't reproduced this error yet I would like to get a better
handle on what people are seeing here. Is it file system corruption
(errors that show up in fsck), or file corruption where fsck does not
report any errors. Also for files that are corrupted do they have the
correct size and
I have placed a test kernel with the above patch at
http://kernel.ubuntu.com/~jj/linux-
image-2.6.31-14-generic_2.6.31-14.48~ext4test1_amd64.deb
It would be good to know if this clears up the corruption problems,
and/or if the warning and stack trace shows up in the logs whether or
not the
I don't think the missing .md5sums files are intrinsically worrying.
I've looked at several of them and they're genuinely missing.
installation-report, for instance (for which I have the source to hand),
just doesn't call dh_md5sums, and the same is true for a number of the
other packages in the
I'm just using plain old ext4 on SSD
--
corruption of large files 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
Here's an example of what I mean:
warcraft scott% wget -q
http://cdimages.ubuntu.com/ubuntu-moblin-remix/daily-live/current/karmic-moblin-remix-i386.iso
warcraft scott% md5sum karmic-moblin-remix-i386.iso
91e4f415767a45617f0cbfc5b0abd19c karmic-moblin-remix-i386.iso
warcraft root# sync
warcraft
http://bugzilla.kernel.org/attachment.cgi?id=23458
--- inode.c.orig2009-10-05 18:18:51.0 +0200
+++ inode.c 2009-10-18 13:16:45.728112813 +0200
@@ -5164,6 +5164,9 @@
} else {
struct ext4_iloc iloc;
+if (inode-i_sb-s_flags MS_RDONLY)
+
Nick: what was the context of that Bugzilla reference, there's no bug#
included
--
corruption of large files 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.
(In case Nick doesn't respond quickly) The patch is referenced in
http://bugzilla.kernel.org/show_bug.cgi?id=14354
Near the end.
--
corruption of large files 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
The reference to that patch is in Comment #90
http://bugzilla.kernel.org/show_bug.cgi?id=14354#c90
--
corruption of large files 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
I did a fresh install from the karmic alt amd64 cd build 20091016 onto
ext4 on LVM. Post install update, and installation of a limited amount
of additional software, I ran a debsums -a on the system, and noticed
the following things:
- debsums claims that the following packages don't have an
On Sat, Oct 17, 2009 at 05:08:49PM -, Steve Beattie wrote:
- the following files were reported as failing their debsums check:
/var/lib/gdm/.gconf.defaults/%gconf-tree.xml
FAILED
/usr/share/applications/gpilotd-control-applet.desktop
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/33804587/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/33804588/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/33804589/BootDmesg.txt
**
There are several open bug reports upstream regarding ext4 corruption,
but it's not clear which, if any, are related to the problems being
observed.
http://bugzilla.kernel.org/show_bug.cgi?id=14354 is one bug that appears
to be linked to the use of the DM layer - if you're following up to this
** Changed in: linux (Ubuntu Karmic)
Status: New = Triaged
--
corruption of large files 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.
--
79 matches
Mail list logo
