NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN316 randomly freezing shared folder on 6.4.0
Hi, I upgraded a client's RN316 to firmware 6.4.0 about 2 days ago. The firmware update reported successful and all seemed ok for about half a day. Now the primary share (2.7TB) of data, has becom...
Do you have ssh enabled? If so, can you go in and run top to see if "[btrfs-cleaner]" shows up and is using lots of CPU? If so, then you may well be experiencing an issue that's been reported in other threads.
Update as at 18:00 today - the extra 4TB hard drive finished resyncing and I now have over 4TB free space available.
The client has closed for the weekend so I don't have any feedback since then, however I will be taking this up again on Monday morning, to establish if the device is now 100% stable again, and performing normally.
Netgear's official position on this was that the ReadyNAS should have 20% - 25% free space available...
Update on Monday morning 26 October 2015:
- NAS is running normally at the moment, after upgrading storage with an additional 4TB last Thursday.
The resync took over 24 hours to complete, but it did finish and the shares were up the whole time.
- Netgear had advised me to run a Balance as well. I first ran a full backup on Saturday, and then I started a balance on Sunday morning.
Bad idea - the balance started out fine, showing up progress as 1% initially, then the device locked up completely (no web interface, no shares available, no ping response).
I decided to wait it out until this morning - still dead, so I had someone onsite pull the power plug on the NAS and switch it back on.
After about 5 minutes the NAS came back up, and the web interface showed the balance had restarted at 0% - there is no way to cancel the balance from within the web interface.
I then used PUTTY to SSH into the device and used the following command to stop the balance:
btrfs fi balance cancel /data
It took a few minutes to cancel, but updating the web interface showed that the balance had been cancelled.
Now the NAS is running normally again, and shares are available. I am just concerned about the fact that I had to cancel the Balance - what effect can this have had on the data?
I can't have the device locking up every time I need to run a balance / defrag / scrub...
...and we're back to where we started.
The laggy RN16 issue persists – today it has dropped the share on the LAN several times, but seemingly not on all workstations.
I am trying to pinpoint if the issue is now AFP / SMB based, or maybe based on something else?
Do I switch AFP / SMB off and on for the share in question, and is that safe to do?
Macs seem to be affected more, so I have been refreshing the DHCP leases for the IP addresses of the Macs just to rule that out - I imagine that an IP conflict somewhere could cause issues.
Could the snapshots (hourly) have an impact on the performance of the device?
I noticed in the logs that the device is also deleting old snapshots on the hour… This was never an issue in 6.2.4 - could it be possible that 6.4.0 has somehow made the snapshot feature buggy and slow - slow enough to cripple the device for approx. 10 minutes at a time?
Update at the end of the day - 28 October 2015...
The ReadyNAS 316 was up to tricks again all day today.
Since about 08:30, up until about 18:00 this evening, it would drop the share whenever it felt like it.
The web interface also went down a few times.
Something that I did notice, and I am hoping that I am onto something here - I took note of the exact times that users went down, and compared that with the device logs.
Old snapshots were auto-deleted at 17 minutes past each hour - so at 09:17am, then at 10:17am etc. - there must be a schedule to control this.
Users went down at approx. half past each hour - 09:30am, then at 10:30am etc.
Snapshots were then created on the hour, each hour.
I am hoping that there is a correlation here - I have since disabled hourly snapshots, and so the hourly auto deletion of snapshots has stopped as well.
I will know during the course of tomorrow if there is a correlation.
It sucks because hourly snapshots are a powerful thing and have saved my butt many times, but I trust that Netgear will fix this performance hit in the next firmware update, if in fact this is the problem...
I would rather have a stable device and fewer snapshots, than a crazy device with a million snapshots...
Holding every thumb that I possess...! :)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
