NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Kish
Mar 22, 2013Aspirant
Questions about OS 6
After reading up on Btrfs, I also do NOT understand the logic in not allowing current ARM and x86 Series owners to upgrade to OS 6. Since Btrfs can do “In-place ext3/4 conversion” (see: https://en.wikipedia.org/wiki/Btrfs). This leads me to question NETGEAR/ReadyNAS concerns over data lose during upgrade to OS 6. Is the implementation of Btrfs an in house hack job? Have you tried upgrades in house, if so, what are the results? Ect.?
20 Replies
Replies have been turned off for this discussion
mdgm wrote: It also doesn't have the expansion limitations that EXT4 in RAIDiator-x86 4.2.x has.
That's irrelevant isn't it?
x86 is EOL'd is it not, never mind that BTRFS is not planned for x86 devices anyway.- StephenBGuru - Experienced User
It is relevant. Overcoming the expansion limitations of ext4 is certainly a positive for btrfs.InTheShires wrote: mdgm wrote: It also doesn't have the expansion limitations that EXT4 in RAIDiator-x86 4.2.x has.
That's irrelevant isn't it?... - tarkeenAspirant
mdgm wrote: It also doesn't have the expansion limitations that EXT4 in RAIDiator-x86 4.2.x has.
So BTRFS is bug fix no new feature. Do why no provide bug fix? - mangroveApprentice
mdgm wrote: It also doesn't have the expansion limitations that EXT4 in RAIDiator-x86 4.2.x has.
How is "expansion limitations" a fault of the file system? - mdgm-ntgrNETGEAR Employee RetiredWhie the limitations with the utilities for creating/expanding the EXT4 filesystem have been fixed some things are required:
1. Update the kernel to one of the latest versions
2. Recreate the volumes with the new utility (would need to backup all data and do a factory default - wipes all data, settings, everything)
3. When expanding an array detect that a volume was created using the newer utility and use the new utility to expand the volume. When expanding an array created using an old utility still use the old expansion utility. - mangroveApprenticeNothing you say has anything to do with the file system. The limitation is not in the file system. So why are you saying there are limitations in the file system?
- file system utilities.
- mdgm-ntgrNETGEAR Employee RetiredYes. You have to recreate the filesystem with the newer utility and then expand it using the newer utility. The newer utility for expansion doesn't work with filesystems created using the older utility.
- mangroveApprenticeIf you are talking about 32-bit vs 64-bit EXT4 inodes, that is completely besides the point. Your argument was that a new filesystem was needed. But the "new filesystem" could just as easily have been 64-bit EXT4. e2fstools support larger volumes than 16TB since 2011. But admittedly the specifics of your points are hard to analyze, as you are not giving any.
You are not exactly helping NTGR by dronelike repeating of the exact same arguments. Especially when they are not good. :D - mdgm-ntgrNETGEAR Employee RetiredYes you can create larger volumes that 16TB, but with the tools present in 4.2.x you need to do a factory reset (wipes all data, settings, everything) with disks in place to get a X-RAID2 volume larger than 16TB in capacity.
With the new versions of the tools you can expand an existing volume beyond 16TB. However the new tools only create/expand new filesystems not those created with the tools present in 4.2.x.
The new versions of the tools have only become available relatively recently.
The expansion limitations present in 4.2.x are:
1. Cannot expand a volume by more than 8TB over the life of the volume.
2. Cannot expand an existing volume to a capacity greater than 16TB.
Related Content
- Jul 15, 2018Retired_Member
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!