*** This bug is a duplicate of bug 197762 ***
https://bugs.launchpad.net/bugs/197762
No, no, no!
Please, can we not tell people to dogpile onto bug #197762?
That bug is so dogpiled as to be useless.
We need to have separate bugs for separate performance problems, instead
of assuming
Comment which I added to bug #541937:
No, no, no!
Please, can we not tell people to dogpile onto bug #197762?
That bug is so dogpiled as to be useless.
We need to have separate bugs for separate performance problems, instead
of assuming that all reported performance problems with USB
On Tue, Apr 20, 2010 at 09:06:13PM -, Jeremy Foshee wrote:
Ted,
I couldn't agree more. I'm not sure I fall into what you would
call someone official in Ubuntu, but I am the Kernel Bug
Triager. My stance on these is to have reporters, with any deviation
from the reported bug they
@allisterbrizan,
Please, do the investigation, and then open a new bug!!!
Your issue with dd clones is completely different from kwstas tsob's
problem in #256 which had to do with source file fragmentation because
of bittorrent.
You see? Both are performance problems, and both are complete
i had similar issues but also when i was trying to copy a file(around 50-700mb
or larger) from my
local hdd to another folder of the same hdd!!!
so what i found out was that this was happening only in files that i had
downloaded with transmission!
What file system were you using on your hdd,
Botond,
Again, I would ask that you take a look at the procedures found here:
https://help.ubuntu.com/community/DiskPerformance
... and then open another bug, complete with details of kernel version,
dstat -D dev when doing a dd if=/dev/zero of=dev bs=32k, and then
the output of dmesg | grep
On Tue, Jul 14, 2009 at 08:45:56PM -0700, Ron Brogden wrote:
Theodore, if I may ask you - are you just another random Linux user
here or are you actually officially associated with Ubuntu in a
support role? I see that you are associated with IBM, have written
some file system utilities and
On Wed, Jul 15, 2009 at 11:33:07AM -, kulight wrote:
I've just remembered why the user base of Linux is so small
I do actually expect my mechanic to find and fix what's wrong with
my car when I just tell him it won't start And I don’t care if it's
the engine the battery or the radiator
Eric,
The problem is that your problem may be very different from other
peoples' problem. First of all, in your test, you are continually
dirtying the page cache with cp /dev/zero /mnt/bigfile.This brings
in filesystem effects, and VM effects, and so it's hard to tell what is
actually going
jamesnmandy,
For someone who 'does not have the time to file a proper bug report',
you seem to have plenty of time to write notes complaining about the
bug. Seriously --- if you aren't willing to help determine the problem
--- and you like GUI solutions --- maybe you should just go back to
Night64:
No, you're using usb-storage device driver for both the pendrive and the
ipod.The messages that you quoted as coming from the ipod just means
that the usb-storage module had gotten unloaded, and when it was loaded
as a module, it prints those lines to the kernel log. The fact that
On Wed, May 20, 2009 at 08:48:34PM -, Night64 wrote:
Thanks for the info, Ts'o. But your comment about libusual caught my eye. In
Ubuntu 9.04 this module still shows up, right?
[81601.434729] usbcore: registered new interface driver libusual
Oops, sorry, that's what I get for not
Ulrich --- if you have time to try to do more tests, may I gently
suggest that you start a new Launchpad bug?Drop a pointer from in
this launchpad bug number to the new one, but let's do all of the
experimentation on a new launchpad bug. There are a couple of reasons
for this:
(1)
For people who are seeing this --- try booting the kernel with the
mem= command line option and see if this makes a difference. For
example if you have 4 gigs of memory, try using mem=1G; if you have a
gig of memory, try using mem=512M. Does this change how big the file
needs to be before you
Something else to try; I would suggest using dstat with the -D option
(i.e, dstat -D sda,sdb) or iostat 1 (although I find dstat to be a bit
more user friendly) to measure I/O transfer rates. I would recommend
using dd if=/dev/zero of=/media/disk/test.img bs=32k to measure the
transfer rates,
15 matches
Mail list logo
