Slow access over network. Lots of errors

[TorturdChaos]

This is the first FreeNAS file server I have every setup. It has been running since the middle of February 2014 with really no issues.

To start I'm running:

Build FreeNAS-9.2.0-RELEASE-x64 (ab098f4)
Platform Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz
Memory 16336MB

The machine running it is a customer built file server I put together. My knowledge of computers is decent, but somewhat lacking in the area of networking.

Lately we have been having some IP conflicts with DHCP assigning IP to new wireless devices that show up on our network that our customers bring in. (Phones, Tablets, Laptops, etc). So I went into our router (Linksys WRT54G runing DD-WRT) and put in Static Leases for most of our equipment. I already had the FreeNAS file server with a Static Lease, along with the computer that contains our on site backup. But I added the rest of our main computers and our various printers. Applied everything and rebooted the router.
Also recently installed the CrashPlan plugin into FreeNAS but haven't got around to trying to configure it.
Also setup a syslog file on FreeNAS to save all the log files too. Rebooted the file sever for it to go into effect.
Shortly after that we started getting instabilities when browsing files on the file server. Right clicking would cause Windows Explorer to hang or lock up completely. When trying to open a file that is fairly simple and should load almost instantaneously, it would take 15-45 secs to load.

Saving a file is giving occasional errors saying it cannot file the network drive.

This is the information I'm seeing in the messages file and in the print out at the footer of the web GUI:

Code:

May 30 10:34:46 KCENTER avahi-daemon[3411]: Invalid legacy unicast query packet.
May 30 10:34:46 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:34:46 KCENTER avahi-daemon[3411]: Invalid legacy unicast query packet.
May 30 10:34:46 KCENTER avahi-daemon[3411]: Invalid legacy unicast query packet.
May 30 10:34:47 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:34:47 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:34:48 KCENTER avahi-daemon[3411]: Invalid legacy unicast query packet.
May 30 10:34:48 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:34:48 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:34:48 KCENTER avahi-daemon[3411]: Invalid legacy unicast query packet.
May 30 10:34:48 KCENTER avahi-daemon[3411]: Invalid legacy unicast query packet.
May 30 10:34:48 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:34:52 KCENTER last message repeated 5 times
May 30 10:39:08 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:39:09 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:39:09 KCENTER avahi-daemon[3411]: Invalid legacy unicast query packet.
May 30 10:39:09 KCENTER last message repeated 2 times
May 30 10:39:09 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:39:10 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:39:10 KCENTER avahi-daemon[3411]: Invalid legacy unicast query packet.
May 30 10:39:10 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:39:10 KCENTER avahi-daemon[3411]: Invalid legacy unicast query packet.
May 30 10:39:10 KCENTER avahi-daemon[3411]: Invalid legacy unicast query packet.
May 30 10:39:10 KCENTER avahi-daemon[3411]: Received response from host 192.168.1.154 with invalid source port 61207 on interface 'lagg0.0'
May 30 10:39:14 KCENTER last message repeated 6 times
May 30 10:59:51 KCENTER smbd[10392]: [2014/05/30 10:59:51.152806,  0] smbd/oplock.c:330(oplock_timeout_handler)
May 30 10:59:51 KCENTER smbd[10392]:  Oplock break failed for file CustomerFiles/CINDY INABNIT/INABNIT LANE 6X24 STREET SIGN.eps -- replying anyway
May 30 11:09:01 KCENTER notifier: Performing sanity check on Samba configuration: OK
May 30 11:09:01 KCENTER notifier: Reloading nmbd.
May 30 11:09:01 KCENTER notifier: Reloading smbd.
May 30 11:09:01 KCENTER notifier: Stopping avahi-daemon.
May 30 11:27:49 KCENTER nmbd[9809]: [2014/05/30 11:27:49.548814,  0] nmbd/nmbd_namequery.c:109(query_name_response)
May 30 11:27:49 KCENTER nmbd[9809]:  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.251 for name KALCOPY<1d>.
May 30 11:27:49 KCENTER nmbd[9809]:  This response was from IP 192.168.1.120, reporting an IP address of 192.168.1.120.
May 30 11:47:58 KCENTER nmbd[9809]: [2014/05/30 11:47:58.206779,  0] nmbd/nmbd_namequery.c:109(query_name_response)
May 30 11:47:58 KCENTER nmbd[9809]:  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.251 for name KALCOPY<1d>.
May 30 11:47:58 KCENTER nmbd[9809]:  This response was from IP 192.168.1.120, reporting an IP address of 192.168.1.120.
May 30 12:08:20 KCENTER nmbd[9809]: [2014/05/30 12:08:20.823254,  0] nmbd/nmbd_namequery.c:109(query_name_response)
May 30 12:08:20 KCENTER nmbd[9809]:  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.251 for name KALCOPY<1d>.
May 30 12:08:20 KCENTER nmbd[9809]:  This response was from IP 192.168.1.120, reporting an IP address of 192.168.1.120.
May 30 12:13:26 KCENTER nmbd[9809]: [2014/05/30 12:13:26.201067,  0] nmbd/nmbd_namequery.c:109(query_name_response)
May 30 12:13:26 KCENTER nmbd[9809]:  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.251 for name KALCOPY<1d>.
May 30 12:13:26 KCENTER nmbd[9809]:  This response was from IP 192.168.1.120, reporting an IP address of 192.168.1.120.
May 30 12:18:17 KCENTER smbd[7607]: [2014/05/30 12:18:17.308050,  0] smbd/process.c:244(read_packet_remainder)
May 30 12:18:17 KCENTER smbd[7607]:  read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_IO_TIMEOUT.
May 30 12:18:26 KCENTER nmbd[9809]: [2014/05/30 12:18:26.912991,  0] nmbd/nmbd_namequery.c:109(query_name_response)
May 30 12:18:26 KCENTER nmbd[9809]:  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.251 for name KALCOPY<1d>.
May 30 12:18:26 KCENTER nmbd[9809]:  This response was from IP 192.168.1.120, reporting an IP address of 192.168.1.120.
May 30 12:43:51 KCENTER nmbd[9809]: [2014/05/30 12:43:51.207500,  0] nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
May 30 12:43:51 KCENTER nmbd[9809]:  *****
May 30 12:43:51 KCENTER nmbd[9809]:
May 30 12:43:51 KCENTER nmbd[9809]:  Samba name server KCENTER is now a local master browser for workgroup KALCOPY on subnet 192.168.1.251
May 30 12:43:51 KCENTER nmbd[9809]:
May 30 12:43:51 KCENTER nmbd[9809]:  *****
May 30 13:02:06 KCENTER smbd[15019]: [2014/05/30 13:02:06.543855,  0] smbd/oplock.c:330(oplock_timeout_handler)
May 30 13:02:06 KCENTER smbd[15019]:  Oplock break failed for file CustomerFiles/Nomad Global Communication/Placards/Part# 411410 - WINCH CONTROL/COMPRESSOR.eps -- replying anyway
May 30 13:02:23 KCENTER smbd[11369]: [2014/05/30 13:02:23.270663,  0] smbd/oplock.c:330(oplock_timeout_handler)
May 30 13:02:23 KCENTER smbd[11369]:  Oplock break failed for file CustomerFiles/Thumbs.db -- replying anyway
May 30 13:02:24 KCENTER smbd[11369]: [2014/05/30 13:02:24.092848,  0] smbd/oplock.c:330(oplock_timeout_handler)
May 30 13:02:24 KCENTER smbd[11369]:  Oplock break failed for file CustomerFiles/Buckles Bucket Seat/bc buckel.indd -- replying anyway
May 30 13:02:28 KCENTER smbd[11369]: [2014/05/30 13:02:28.843850,  0] smbd/oplock.c:330(oplock_timeout_handler)
May 30 13:02:28 KCENTER smbd[11369]:  Oplock break failed for file CustomerFiles/Buckle's Bucket Seat/Thumbs.db -- replying anyway
May 30 13:02:30 KCENTER smbd[11369]: [2014/05/30 13:02:30.314848,  0] smbd/oplock.c:330(oplock_timeout_handler)
May 30 13:02:30 KCENTER smbd[11369]:  Oplock break failed for file CustomerFiles/Buckle's Bucket Seat/96x8 Banner.pdf -- replying anyway
May 30 13:04:50 KCENTER smbd[15137]: [2014/05/30 13:04:50.639027,  0] smbd/oplock.c:330(oplock_timeout_handler)
May 30 13:04:50 KCENTER smbd[15137]:  Oplock break failed for file CustomerFiles/big mountain/big mtn.PDF -- replying anyway
May 30 13:09:07 KCENTER smbd[15243]: [2014/05/30 13:09:07.063819,  0] smbd/oplock.c:330(oplock_timeout_handler)
May 30 13:09:07 KCENTER smbd[15243]:  Oplock break failed for file CustomerFiles/Nomad Global Communication/Placards/Part# 411410 - WINCH CONTROL/COMPRESSOR.eps -- replying anyway
May 30 13:14:15 KCENTER smbd[15246]: [2014/05/30 13:14:15.024991,  0] smbd/oplock.c:330(oplock_timeout_handler)
May 30 13:14:15 KCENTER smbd[15246]:  Oplock break failed for file CustomerFiles/Nomad Global Communication/Placards/Part# 411410 - WINCH CONTROL/COMPRESSOR.eps -- replying anyway

Can someone tell me what they mean and possibly how to fix them?

Thanks

 

[cyberjock]

Well, I'll ask the typical tripwire questions...


1. Are you 100% sure your network topology can benefit from LAGG? If not it's added complexity and leads into #2...
2. Are you sure your network hardware supports LAGG? If not you shouldn't be using it. Cheap hardware(aka home stuff) doesn't support LAGG. If it does support LAGG that leads into #3...
3. Are you sure your network hardware is properly setup? If not you probably shouldn't be using LAGG. ;)

(You noticing the pattern with LAGG yet? If you don't know for 100% certain what you are doing, you shouldn't be trying to use it.)

4. What's your pool design and all hardware in the server?

 

[hammong]

What kind of switch is your FreeNAS plugged into, and did you explicit configure LACP/802.11ad link aggregation on it? If you've got it plugged into some consumer-grade non-managed switch, LAGG isn't going to work.... at all.

Greg

 

[TorturdChaos]

Well, I'll ask the typical tripwire questions...


1. Are you 100% sure your network topology can benefit from LAGG? If not it's added complexity and leads into #2...
2. Are you sure your network hardware supports LAGG? If not you shouldn't be using it. Cheap hardware(aka home stuff) doesn't support LAGG. If it does support LAGG that leads into #3...
3. Are you sure your network hardware is properly setup? If not you probably shouldn't be using LAGG. ;)

(You noticing the pattern with LAGG yet? If you don't know for 100% certain what you are doing, you shouldn't be trying to use it.)

4. What's your pool design and all hardware in the server?

1- No I'm not 100% sure. My thoughts on it was I have 2 ethernet cards on the mobo, with 2 spare gigabite ethernet ports on the switch, with 5 computers and 7 printers pulling data from the file server.
2- From what I can tell yes my switch does support LAGG The Switch is a Linksys SRW248G4 v1.1 Switch. According to the data sheet (pg 2):

Availability

Link Aggregation Link Aggregation using IEEE 802.3ad LACP

Up to 8 ports in up to 8 trunks

I know its a little strange to have consumer grade router running DHCP for a switch like that but so far it has been working. This setup as been working pretty much flawlessly from middle of Feb until I posted.
3- I think its properly setup. Really all I did was follow a guide for setting up LAGG on FreeNAS
4- Here are the specs:
Intel Xeon E3-1240 V2 Ivy Bridge 3.4GHz
Mobo
SUPERMICRO MBD-X9SCL-F-O
Case
Fractal Design Define R4
PSU
Seasonic 360W 80PLUS Gold ATX12V Power Supply SSR-360GP
Ram
Kingston 16GB (2 x 8GB) 240-Pin DDR3 SDRAM ECC Unbuffered DDR3 1333 Server Memory Model KVR1333D3E9SK2/16G
HDD's
Western Digital 2 TB 3.5-Inch WD Se x5 in a Raid-Z3



I can disable the LAGG and see if it helps any.

 

[hammong]

Your Linksys SRW248G4 does indeed support LACP, but you absolutely MUST configure the switch with a trunk group for the server connection. E.g. you plug your server into two of the ports on the switch (say port 1 and port 2) and then configure port 1 and 2 on the switch to be a member of a trunk group. Without that crucial step, you have 1/2 of a LAGG set up and it's going to end up causing you duplicate or dropped packets as a result. Pretty much what you have now.

Greg

 

[cyberjock]

Yeah, what hammong said. Keep in mind if you aren't intimately familiar with LACP you should just not try to use it, or be ready to do a ton of experimenting. Unfortunately, all we can do is tell you how to setup LACP for FreeNAS. Anything else is outside the scope of this forum and you may or may not get any answers to questions related to your network switch, etc.

LACP/LAGG is a nightmare because everyone thinks its like getting a free beer. It's not. You have to know what you are doing, it has to apply for your situation(which I don't feel that it does with 5 users...) and it has to actually function properly(which many switches don't for some stupid reason).

 

[TorturdChaos]

I deleted the LAGG settings and everything seems to be running much better now.
And I agree it does sound like "Free Beer". My thought on it when I first looked it up was "Hey great! I can edit a large Photoshop file and so can the Small Format guy, and we each will used a different ethernet port!"
But I feeling now that is way out of my league to setup correctly. Maybe this winter when we usually slow down I will try to educate myself on it.

Thanks for all your help hammong & cyberjock.