NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNas 102 = Unusable frustrating junk! - now what?
Firmware 6.10.4 hotfix 1 - RAID 1 This unit has become a comedy of errors. It seems anything I try to do with it, it just gives errors. Yeah, it's end of life. But its not really that old and it...
I didn't really mean I'd fill it to 100%, but I'd like the ability to fill it...i.e. not get errors that it is full when it isn't.
I have about 600GB of free space. And I just freed up more by cleaning up old snapshots.
Here's the top part of btrfs.log
Label: '2fe56952:data' uuid: f3768221-8da7-44f9-8fe1-fc703e7af6fd Total devices 1 FS bytes used 2.14TiB devid 1 size 2.72TiB used 2.72TiB path /dev/md127 === filesystem /data === Data, single: total=2.70TiB, used=2.13TiB System, DUP: total=8.00MiB, used=352.00KiB System, single: total=4.00MiB, used=0.00B Metadata, DUP: total=10.50GiB, used=10.00GiB Metadata, single: total=8.00MiB, used=0.00B GlobalReserve, single: total=512.00MiB, used=0.00B
Ok, that's what I thought....working on scouring up a bunch of old drives now to do so.
chadwixk wrote:Here's the top part of btrfs.log
Label: '2fe56952:data' uuid: f3768221-8da7-44f9-8fe1-fc703e7af6fd Total devices 1 FS bytes used 2.14TiB devid 1 size 2.72TiB used 2.72TiB path /dev/md127
Note that third line
size 2.72TiB used 2.72TiB
That means that the space on the data volume is fully allocated.
When you delete data if a chunk is emptied it is returned to unallocated space. It can take some time for this to happen. When you delete an old snapshot all the newer snapshots are updated recursively, I think which can take some time.
Note to free up space by deleting snapshots, all snapshots that contain some deleted data must be deleted.
So if you added a file on the 1st January and deleted it on the 1st March you'd need to delete all snapshots from and including the time on 1st January when the data was added onwards through to and including the time on 1st March when the data was deleted. If you don't do that then deleting that data doesn't free up space.
If deleting all the snapshots that contain some data doesn't change the allocations being full then you could try a balance from SSH with some special parameters e.g. -dusage=1. Though it could fail due to not enough space in which case the workaround is to temporarily add some storage e.g. a USB disk so that a balance can be run and then when space is freed up to run commands to remove the USB disk from the data volume.
chadwixk wrote:Data, single: total=2.70TiB, used=2.13TiBOk, that's what I thought....working on scouring up a bunch of old drives now to do so.
So we have 2.70TiB allocated to data of which 2.13TiB is in use.
chadwixk wrote:Metadata, DUP: total=10.50GiB, used=10.00GiB
0.5GiB of that metadata allocation is reserved so the metadata is full. What's needed is to return some space from data to unallocated space so that it can be allocated to metadata.
chadwixk wrote:Ok, that's what I thought....working on scouring up a bunch of old drives now to do so.
What does your initrd.log look like?
If you look further in btrfs.log do you see some of the deleted snapshots are still in purge?
I saw that line, but also right above it it shows that only 2.14TB is used, which also corresponded with what the web interface GUI showed...about 25% free space.
Total devices 1 FS bytes used 2.14TiB
Also this seems to support that there is ~600GB of free space:
Data, single: total=2.70TiB, used=2.13TiB
This seems to directly contradict each other? Why does this show it is full? :
size 2.72TiB used 2.72TiB
Here's the initrd.log
[2015/08/27 01:19:39] Factory default initiated due to new disks (no RAID, no partitions)! [2015/08/27 01:19:45] Defaulting to X-RAID2 mode, RAID level 1 [2015/08/27 01:20:17] Factory default initiated on ReadyNASOS 6.2.0 (ReadyNASOS). [2015/08/30 07:20:21] Updated from ReadyNASOS 6.2.0 (ReadyNASOS) to 6.2.5 (ReadyNASOS). [2015/12/02 09:50:47] Updated from ReadyNASOS 6.2.5 (ReadyNASOS) to 6.4.1 (ReadyNASOS). [2016/11/29 20:25:15] Updated from ReadyNASOS 6.4.1 (ReadyNASOS) to 6.5.0 (RC3). [2017/07/15 16:12:29 UTC] Updated from ReadyNASOS 6.5.0 (RC3) to 6.7.5 (ReadyNASOS). [2018/11/15 21:22:23 UTC] Updated from ReadyNASOS 6.7.5 (ReadyNASOS) to 6.9.4 (ReadyNASOS). [2019/02/05 06:55:49 UTC] Updated from ReadyNASOS 6.9.4 (ReadyNASOS) to 6.9.5 (ReadyNASOS). [2019/12/03 10:12:14 UTC] Updated from ReadyNASOS 6.9.5 (ReadyNASOS) to 6.10.2 (ReadyNASOS). [2021/03/04 03:57:07 UTC] Updated from ReadyNASOS 6.10.2 (ReadyNASOS) to 6.10.4 (ReadyNASOS).
So after deleting multiple snapshots, and my son accidentally tripping the breaker that my NAS is on, restarting the NAS which is now reindexing, I am able to now Save config changes. Turning off the Volume Quota, adding Dropbox uploads and last night's robocopy backup script worked, without any disk full errors!
So I considere this mostly solved. My only remaining issue is that I was having these errors when the disk seemed to be reporting that it had ~600GB of 2.7TB of free space, which is a decent amount of space. So I'm not convinced that it was truly full, and hence not sure of what the root problem was, and further, not convinced it won't happen again nor how to fix if it does. Time will tell I guess.
Current btrfs.log:
Label: '2fe56952:data' uuid: f3768221-8da7-44f9-8fe1-fc703e7af6fd Total devices 1 FS bytes used 1.53TiB devid 1 size 2.72TiB used 2.72TiB path /dev/md127 === filesystem /data === Data, single: total=2.70TiB, used=1.52TiB System, DUP: total=8.00MiB, used=352.00KiB System, single: total=4.00MiB, used=0.00B Metadata, DUP: total=10.50GiB, used=3.00GiB Metadata, single: total=8.00MiB, used=0.00B GlobalReserve, single: total=512.00MiB, used=0.00B
It still shows in this one line that it is full, so I don't think that means its full, but that it is fully reserved for use or something
devid 1 size 2.72TiB used 2.72TiB path /dev/md127
It is now reporting only being a bit over 50% used:
Data, single: total=2.70TiB, used=1.52TiB
Metadata, DUP (not sure the diff between DUP and single), is lower, but originally, it still had 500MB of unused space, I'd think that would be plenty and there was 600GB of free space it could've pulled from if it needed more, and I'd hope the logic would be there to do so.
The space is fully allocated. There's a difference between allocation and what is in use of the allocation. That 512MiB in metadata is in the GlobalReserve. The system had nowhere to store additional metadata and with the space on the volume fully allocated it couldn't allocate any more space to metadata. Now that you have metadata allocation available to use you can write to the volume again.
You may wish to do a balance of the data volume. That will move data around so that chunks are emptied and returned to unallocated space.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
