NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Fri Apr 19, 2024 8:34 am

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 3 posts ] 
Author Message
PostPosted: Thu May 31, 2012 1:52 pm 
Offline

Joined: Fri Feb 25, 2005 11:50 pm
Posts: 139
Always believed I was bypassing all network functions but am seeing these errors:


eth0: VIA Rhine II at 0x1e800, 00:13:d4:e3:bd:f2, IRQ 11.
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link cde1.
eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000002.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000002.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000002.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000002.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000002.
eth0: Too much work at interrupt, status=0x00000001.
eth0: Too much work at interrupt, status=0x00000002.
eth0: Too much work at interrupt, status=0x00000001.
eth0 Link encap:Ethernet HWaddr 00:13:D4:E3:BD:F2
inet addr:192.168.0.160 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1118428967 errors:0 dropped:13794 overruns:0 frame:0
TX packets:729649601 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:295215595 (281.5 MiB) TX bytes:3057644553 (2.8 GiB)
Interrupt:11 Base address:0xe800


Top
 Profile  
 
PostPosted: Thu May 31, 2012 3:34 pm 
Offline

Joined: Fri Jan 12, 2007 4:27 am
Posts: 577
Location: Scotland
If you're moving \\<server>\Shares\Disk-2 to \\<server>\Shares\Disk-0 then you should be bypassing using the network.

However if you're moving \\<server>\Disk-2 to \\<server>\Disk-0 then you are moving via the client machine.


Top
 Profile  
 
PostPosted: Thu May 31, 2012 3:46 pm 
Offline

Joined: Fri Feb 25, 2005 11:50 pm
Posts: 139
NickC wrote:
If you're moving \\<server>\Shares\Disk-2 to \\<server>\Shares\Disk-0 then you should be bypassing using the network.

However if you're moving \\<server>\Disk-2 to \\<server>\Disk-0 then you are moving via the client machine.



Well, shares to shares.....that's what I'm using - but I still get these network error messages. Pretty bizarre.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 69 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group