OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT!

StephenB wrote:
It might be overly conservative, but It is working as designed. 3.2/4.5 = 71% used.

70%? If that's grounds for a warning, why in the world would someone consider a Readynas unit? A volume should be able to be filled to 90-100%, or else I could use that unusable storage in better ways, like making a RAID6 or RAID10 with a sane file system. To recap:

4x3TB = 12TB in RAID0
4x3TB = 9TB in RAID5 on all sane implementations in the world
4x3TB = 6,3TB in ReadyNAS-BTRFS-RAID5 (if respecting the 70% warning)
4x3TB = 6TB in RAID6
4x3TB = 6TB in RAID10

Why in the world of (multiple expletives) would I choose "slick, almost-working snapshots" over real redundancy? Only a crazy person would do that.

The underlying problem, of course, is that BTRFS has no real concept of "how much space is left":
https://btrfs.wiki.kernel.org/index.php ... e_space.3F
Do note this quote:

it is impossible to give an accurate estimate of the amount of free space on any btrfs filesystem

And because of BTRFS's extremely malign characteristics when the file system gets full, this warning has to be "overly conservative", indeed. But don't fret! These malign characteristics:

will eventually be worked around properly

Wow! feelsgoodman.jpg considering that this hasn't been worked out yet after, like what, six years of development.

mdgm wrote:
Like any PC when the volume gets very full, performance may suffer.

This is so untrue it hurts. "Performance" doesn't suffer when a spinning disk is "very full"; fragmentation (and to some extent longer seeks + the following rotational latency) does that, and you can fill a volume (you know, DATA STORAGE, the thing a NAS is made for) without fragmenting it just fine. Then the only "performance" "suffering" is the difference in transfer rates between outer and inner zones, which is because of the physical properties of spinning disks with constant angular velocity. But, of course, as usual your #1 priority is to make NTGR look better.

In reality, this warning is because BTRFS behaves very badly when the file system is full, and you might be unable to even delete files. And this is what you get when you use beta file systems in production units.