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
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.
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
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
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
@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
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
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
@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
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
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
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
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
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
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,
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
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
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
18 matches
Mail list logo
