NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
BJB
Jan 19, 2016Aspirant
Upgrading my RN104 from 6.1.9
Greetings. I received some great advice on another thread but that was quite a while ago and it is closed. And I am just now finally getting around to this upgrade. My RN104 is on version 6.1.9...
- Jan 26, 2016
This is done.
Thanks,
BJB
mdgm-ntgr
Jan 24, 2016NETGEAR Employee Retired
Please send in a fresh set of logs downloaded after the update to 6.2.5
BJB
Jan 26, 2016Aspirant
This is done.
Thanks,
BJB
- BJBJan 26, 2016Aspirant
FYI, what I meant by "this is done" is I sent the logs. :smileyhappy:
May have replied to the wrong post .
BJB
- mdgm-ntgrJan 27, 2016NETGEAR Employee Retired
Bit-rot protection and snapshots will lead to a lot of fragmentation if used on shares that you backup to.
Your snapshots were not upgraded when you updated to 6.2.5. Do you still need those?
- BJBJan 27, 2016Aspirant
mdgm,
Since you are commenting on my snapshots I assume you got my logs? I do not need those snapshots. However I did not receive any message that they were not updated. Since they were not updated can I delete them in 6.2.5?
As far as share and bitrot settings, here are my shares. I have a backup share that is strictly for disk images. A picture share where images are copied there and stay there. No deleting. And a video share where things are added and occasionally streamed. No deleting. Just let me know the best share and bitrot settings for each or all of these.
And if I have to delete those shares or something let me know how and when. I guess I need to sort that out, set the right share and bitrot settings, then run my maintenance stuff, then upgrade whenever I want.
Thanks again,
BJB
- mdgm-ntgrJan 27, 2016NETGEAR Employee Retired
I can remove these remotely. Would be best to do this before updating to 6.4 seeing how full your volume is.
Generally this is true: If files are regularly being modified in place then bitrot is bad. If you are mainly adding files but not editing them then bitrot is good.
- StephenBJan 27, 2016Guru - Experienced User
mdgm wrote:
Generally this is true: If files are regularly being modified in place then bitrot is bad. If you are mainly adding files but not editing them then bitrot is good.
This is certainly true for snapshots - when files are modified in place, they end up fragmented, which will hurt performance.
AFAIK bitrot protection only needs the btrfs checksums. I don't see any particular reason why modifying files in place is a problem for the file system or for bitrot protection itself, as long as there are no snapshots kept for the share. Can you elaborate a bit more on your thinking here?
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!