NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AMRivlin
Mar 20, 2013Apprentice
OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT!
Update: It is now unofficially possible using NTGR images to update legacy hardware to os6.X See Post #3, for directions to install 6.2.1 on x86 Ultra and Pro Models. (ARM NOT SUPPORTED by this OS) ...
- Jan 21, 2016
mdgm and I have decided that its time to lock this thread. So please do post any new OS6 on Legacy issues on their own threads.
xsnrg
Nov 08, 2013Aspirant
A few comments. First, it would be nice to be able to select the filesystem, but even with btrfs there are other options that could be explored. There is a defrag mount option, which probably is not ideal for a nas, but there is the option, when a new sub is created (a share in readynas speak) to set an attribute on the sub +C. This disables operations of CoW, and would change some important things on how that sub operates. Netgear would have to call out what the difference is and how it affects things like snapshots, but it is about the only option I see to use btrfs for VM images. The attribute change/option would allow the rest of the NAS, if desired, to still use all the functions of btrfs.
Netgear should NOT default a new share to have snapshots on. This is a bad idea.
Finally, messing with the vm areas of the kernel should only be done if you are absolutely sure you know what you are doing. This is not saying you don't just a warning for others reading this. An example, vm.swappiness affects the ratio of used memory in the system to the amount, and starting place for swapping memory to disk. My NAS has it set to 0 which I think is a good setting. This causes the machine to always prefer memory to disk swap until memory is completely exhausted. Setting it higher may give you more disk cache, but as soon as you start swapping things out of system memory, you pay the price when it is needed again. In an OS made to be as light as possible, which I hope is the case, most of the things in memory are important, even if periodically, to the operation of the system.
Netgear should NOT default a new share to have snapshots on. This is a bad idea.
Finally, messing with the vm areas of the kernel should only be done if you are absolutely sure you know what you are doing. This is not saying you don't just a warning for others reading this. An example, vm.swappiness affects the ratio of used memory in the system to the amount, and starting place for swapping memory to disk. My NAS has it set to 0 which I think is a good setting. This causes the machine to always prefer memory to disk swap until memory is completely exhausted. Setting it higher may give you more disk cache, but as soon as you start swapping things out of system memory, you pay the price when it is needed again. In an OS made to be as light as possible, which I hope is the case, most of the things in memory are important, even if periodically, to the operation of the system.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!