Console full of DNS stuff

[dtemp]

Here is a sample of 1 minute worth of stuff in my console:

May 8 23:35:05 freenas smbd[22185]: [2014/05/08 23:35:05.595231, 0] ../source3/lib/util_sock.c:941(matchname)
May 8 23:35:05 freenas smbd[22185]: matchname: host name/name mismatch: 192.168.1.5 != (NULL)
May 8 23:35:05 freenas smbd[22185]: [2014/05/08 23:35:05.595326, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
May 8 23:35:05 freenas smbd[22185]: matchname failed on 192.168.1.5
May 8 23:35:17 freenas smbd[22198]: [2014/05/08 23:35:17.875358, 0] ../source3/lib/util_sock.c:941(matchname)
May 8 23:35:17 freenas smbd[22198]: matchname: host name/name mismatch: 192.168.1.3 != (NULL)
May 8 23:35:17 freenas smbd[22198]: [2014/05/08 23:35:17.875450, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
May 8 23:35:17 freenas smbd[22198]: matchname failed on 192.168.1.3
May 8 23:35:54 freenas smbd[22210]: [2014/05/08 23:35:54.665608, 0] ../source3/lib/util_sock.c:941(matchname)
May 8 23:35:54 freenas smbd[22210]: matchname: host name/name mismatch: 192.168.1.4 != (NULL)
May 8 23:35:54 freenas smbd[22210]: [2014/05/08 23:35:54.665729, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
May 8 23:35:54 freenas smbd[22210]: matchname failed on 192.168.1.4

I realize DNS is a bit outside of the scope of FreeNAS forums... but I'd like for these messages to not clog my console. I use an Apple Airport Extreme 5th Gen, which doesn't seem to do "local DNS," and you can only resolve local host names via a bonjour/zeroconf/avahi-daemon kind of thing.

Any tips for making FreeNAS either happy, or telling it to ignore this stuff?

 

[dlavigne]

The "host name database" field in http://doc.freenas.org/index.php/Global_Configuration updates /etc/hosts on FreeNAS. Adding entries for each IP address/hostname pair in the log should fix it.

 

[joeschmuck]

Or you could disable "Hostnames lookup" under the CIFS configuration. Using the above method means you have to add everything that attaches to your network which in most homes these days can be a lot of stuff.

 

[dtemp]

Or you could disable "Hostnames lookup" under the CIFS configuration. Using the above method means you have to add everything that attaches to your network which in most homes these days can be a lot of stuff.

I looked up the doc and it says this setting "allows you to specify hostnames rather than IP addresses in the Hosts Allow or Hosts Deny fields of a CIFS share; uncheck if you only use IP addresses as it saves the time of a host lookup." So this setting means diddly if I'm not using those Host fields, and I could just use IPs if they didn't have dynamic addresses anyway.

Thanks! Seems to have worked. Now I just have it telling me about one drive's unreadable and uncorrectable sectors every little while :)

 

[joeschmuck]

Thanks! Seems to have worked. Now I just have it telling me about one drive's unreadable and uncorrectable sectors every little while :)

If you are getting errors of this nature, your hard drive is dying. If you run 'smartctl -a /dev/adax' (x being your drive you are being warned about), ID's 5, 197, and 198 should be a zero value. Based on what you have said I suspect 197 and 198 are definitely not zero. You have a RAIDZ2 setup so you can handle a drive failure but there is no reason to just wait for it to happen especially if the drive is under warranty.

 

[dtemp]

Thanks for the note. I'm keeping an eye on the situation. The numbers for the drive look hilariously bad. They are posted at the end of this comment. Unless you think I'm an idiot, I think my plan is actually to just sit on it until it gets kicked out of the array. I run biweekly scrubs and weekly long SMART tests. I manually ran a scrub last night, and running "zpool status" showed "Repairing" next to the drive during the scrub (not sure what actually was repaired since the errors are still there). I have a good backup system in case my pool gets hosed.

The drives are all WAY out of warranty. They were collected over years, and are different manufacturers and models. Some were ripped out of USB enclosures (the non-user-serviceable variety). The plan is to wait until my 4TB is ~85% full and then double the RAM to 32GB and swap out the drives for 3TB or 4TB reds; I'd like to avoid having to pick up a $60 1TB drive between now and then, which is probably mid-2015. These odd drives are the only janky part of my system; the rest is new and legit and warrantied. The I in RAID stands for Inexpensive right? ;)

Code:

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate    0x000f  098  084  006    Pre-fail  Always      -      98945696
  3 Spin_Up_Time            0x0003  092  091  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      119
  5 Reallocated_Sector_Ct  0x0033  095  095  036    Pre-fail  Always      -      110
  7 Seek_Error_Rate        0x000f  079  060  030    Pre-fail  Always      -      86233296
  9 Power_On_Hours          0x0032  065  065  000    Old_age  Always      -      30958
10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0
12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      80
184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0
187 Reported_Uncorrect      0x0032  094  094  000    Old_age  Always      -      6
188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0
189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0
190 Airflow_Temperature_Cel 0x0022  062  047  045    Old_age  Always      -      38 (Min/Max 23/43)
194 Temperature_Celsius    0x0022  039  053  000    Old_age  Always      -      39 (0 17 0 0 0)
195 Hardware_ECC_Recovered  0x001a  043  017  000    Old_age  Always      -      98945696
197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      8
198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      8
199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      0

 

[joeschmuck]

Yes, the ID# 5 value is of huge concern but so long as you have your important data backed up elsewhere, I see no issue with just waiting for it to fail since you are running a RAIDZ2 however it's it not what I'd recommend. My personal recommendation is to replace this one drive as soon as possible, even if you have to wait for a drive to go on sale. If you want to use 3TB or 4TB drives, just plop one in. Of course you will not see the benefit of the new drive until you replace all your drives but at least your data is safe. Once you replace that last drive your pool size will jump to the full capacity of all the drives.

 

[dtemp]

Are you a wizard? Woke up this morning to an email saying my pool was degraded. Replaced and resilvered with a 2TB drive I had laying around. Now there is another disk with different types of errors, the type that don't show up with "smartctl -a" but are write errors showing on "zpool status;" array isn't degraded though.

 

[joeschmuck]

Your write errors could be a SATA cable issue. If they just started because you got into the case then maybe you bumped something?

 

[dtemp]

That's totally possible. I did a "zpool clear poolname" and we'll see what happens. Maybe I should cold-swap instead of hot-swap.

 

[joeschmuck]

I prefer a cold swap to a hot swap.

 

[KempelofDoom]

So am I reading his results right for 5, 197 and 198 that the values were 110, 8, & 8 respectively? Do we have a thread that explains the smart command output for dummies like myself? I see all those numbers and get lost in the aether.

 

[cyberjock]

You can figure out what all that stuff means with a few Google searches. That's how I learned about them.

 

[joeschmuck]

You can figure out what all that stuff means with a few Google searches. That's how I learned about them.

Ditto !