On Tue, 2010-08-10 at 17:27 +0300, Gilboa Davara wrote:
> > I mentioned this in my first post. It doesn't happen with copies to the
> > local HD.
> >
> > poc
> >
>
> OK. Next step.
> Try ping flooding (ping -s 1400 -f, as root) another host on your
> network. Do you see the same results?
> How man
> I mentioned this in my first post. It doesn't happen with copies to the
> local HD.
>
> poc
>
OK. Next step.
Try ping flooding (ping -s 1400 -f, as root) another host on your
network. Do you see the same results?
How many packets are lost (if any)?
- Gilboa
--
users mailing list
users@lists.fe
On Tue, 2010-08-10 at 10:49 +0300, Gilboa Davara wrote:
> On Tue, Aug 10, 2010 at 6:30 AM, Patrick O'Callaghan
> wrote:
> > $ cat /proc/interrupts
> > CPU0 CPU1
> > 31: 58723167 0 PCI-MSI-edge eth0
> > 23:1445442 0 IO-APIC-fasteoi ehci_hcd:usb2,
On Tue, Aug 10, 2010 at 6:30 AM, Patrick O'Callaghan
wrote:
> $ cat /proc/interrupts
> CPU0 CPU1
> 31: 58723167 0 PCI-MSI-edge eth0
> 23:1445442 0 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb5
Ethernet is using MSI interrupts with no sharing.
I
On Tue, 2010-08-10 at 04:39 +0300, Gilboa Davara wrote:
> >> Are you seeing perhaps a common ethernet and disk or ethernet and
> video
> >> using the same interrupt?
> >
> > Not as far as I can tell (using 'lshw').
> >
> > poc
> >
>
> What's the output of /proc/interrupts
$ cat /proc/interrupts
On Tue, Aug 10, 2010 at 4:19 AM, Patrick O'Callaghan
wrote:
> On Mon, 2010-08-09 at 20:12 -0400, John Mellor wrote:
>> On Mon, 2010-08-09 at 19:10 -0430, Patrick O'Callaghan wrote:
>> > On Mon, 2010-08-09 at 15:46 -0400, Tom Horsley wrote:
>> > > Use rsync to do the copying and come up with a --bw
On Mon, 2010-08-09 at 20:12 -0400, John Mellor wrote:
> On Mon, 2010-08-09 at 19:10 -0430, Patrick O'Callaghan wrote:
> > On Mon, 2010-08-09 at 15:46 -0400, Tom Horsley wrote:
> > > Use rsync to do the copying and come up with a --bwlimit
> > > option that will keep it from completely clogging the
On Mon, 2010-08-09 at 19:10 -0430, Patrick O'Callaghan wrote:
> On Mon, 2010-08-09 at 15:46 -0400, Tom Horsley wrote:
> > Use rsync to do the copying and come up with a --bwlimit
> > option that will keep it from completely clogging the
> > network and let it catch its breath sometimes.
>
> I don'
On Mon, 2010-08-09 at 15:46 -0400, Tom Horsley wrote:
> Use rsync to do the copying and come up with a --bwlimit
> option that will keep it from completely clogging the
> network and let it catch its breath sometimes.
I don't think clogging the network is really the issue but when I
throttled it t
On Mon, 2010-08-09 at 13:45 -0700, Konstantin Svist wrote:
> On 08/09/2010 12:36 PM, Patrick O'Callaghan wrote:
> > I've been copying some large (several GB) files from my local system to
> > a NAS server on my LAN, using NFS.
> >
> > The local files are on an external USB drive (Iomega 500GB unit)
On Mon, 2010-08-09 at 13:45 -0700, Konstantin Svist wrote:
> On 08/09/2010 12:36 PM, Patrick O'Callaghan wrote:
> > I've been copying some large (several GB) files from my local system to
> > a NAS server on my LAN, using NFS.
> >
> > poc
>
> Usually you see this kind of problem when your HDD is
On 08/09/2010 12:36 PM, Patrick O'Callaghan wrote:
> I've been copying some large (several GB) files from my local system to
> a NAS server on my LAN, using NFS.
>
> The local files are on an external USB drive (Iomega 500GB unit) on a
> USB 2 port. The NAS server is also Iomega, an ix-200. The n
On Mon, 09 Aug 2010 15:06:11 -0430
Patrick O'Callaghan wrote:
> Any thoughts on this would be welcome.
I can't explain the problem (that would be for someone who
understands the network code in linux :-), but I can
offer a workaround gimmick:
Use rsync to do the copying and come up with a --bwli
I've been copying some large (several GB) files from my local system to
a NAS server on my LAN, using NFS.
The local files are on an external USB drive (Iomega 500GB unit) on a
USB 2 port. The NAS server is also Iomega, an ix-200. The network switch
is a Belkin Wireless G with 100Mbps Ethernet por
14 matches
Mail list logo
