× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Unable to erase inaccessible snapshots in ReadyNAS 424

lpkvh08
Tutor

Unable to erase inaccessible snapshots in ReadyNAS 424

Hi,

I have a ReadyNAS 424 and even after I have disabled and deleted all the snapshots in it. But still 1-1.5 TB s space is alloted to it. I have tried the methos from,

https://forum1.netgear.com/t5/Using-your-ReadyNAS-in-Business/Snapshots-reclaiming-storage-space/td-...

but it still does not work. I tried scrubbing and balancing after, but still no use. The snapshot allocation remains unchanged.

 

I have searched all over teh internet and even tried to delete the snapshots via SSH. But it does not let me. I tried saturating the drive space to empty. But still the snapshots do not disappear.

 

I do not understand why this is happening. I cannot reset my NAS now since I do not have spare drives to dump the data temporarily. Can anyone help me? Netgear engineers and technicians? Power users? Please help me with this issue. Thank you.

 

Firmware ver 6.10.1

Model: RN424|ReadyNAS 424 – High-performance Business Data Storage - 4-Bay
Message 1 of 6

Accepted Solutions
StephenB
Guru

Re: Unable to erase inaccessible snapshots in ReadyNAS 424


@lpkvh08 wrote:

 

ERROR: Could not destroy subvolume/snapshot: Directory not empty

 


The command isn't recursive, so it won't delete subvolumes inside another subvolume. So if you just tried deleting the main snapshot folder for the share with that command, it will fail.

 

Try listing the snapshots with 

# btrfs subvolume list -s /data

and then delete each snapshot (one at a time) using the full path name.

 

The other approach is to destroy the volume, recreate it, reconfigure the shares, and restore the files from your backup.

View solution in original post

Message 5 of 6

All Replies
lpkvh08
Tutor

Re: Unable to erase inaccessible snapshots in ReadyNAS 424

Attached is screenshot from my NAS web UI page.

Message 2 of 6
StephenB
Guru

Re: Unable to erase inaccessible snapshots in ReadyNAS 424

How did you try to delete the snapshots with ssh?

 

You need to log in as root (NOT admin) and you need to use btrfs commands (NOT rm).  For instance

# btrfs subvolume delete -c <path>

where path is the full path of the subvolume.

 

After you've deleted them, it can take some time for the space to be reclaimed.  I suggest running a balance afterwards (from the volume settings wheel).

Message 3 of 6
lpkvh08
Tutor

Re: Unable to erase inaccessible snapshots in ReadyNAS 424

Hi. Thank you for the reply. I have previously tried deleting using SSH and with root user privileges. I used various Linux commands to delete. But I got errors saying they were read-only file system. I also tried to change permissions with chmod -Rf 777. But nothing worked.

 

I tried the command you gave just now as well. But it returned this,

ERROR: Could not destroy subvolume/snapshot: Directory not empty

 

Any other method to delete these read-only folders along with the complete directory structure in one go? Please let me know. Thank you.

Message 4 of 6
StephenB
Guru

Re: Unable to erase inaccessible snapshots in ReadyNAS 424


@lpkvh08 wrote:

 

ERROR: Could not destroy subvolume/snapshot: Directory not empty

 


The command isn't recursive, so it won't delete subvolumes inside another subvolume. So if you just tried deleting the main snapshot folder for the share with that command, it will fail.

 

Try listing the snapshots with 

# btrfs subvolume list -s /data

and then delete each snapshot (one at a time) using the full path name.

 

The other approach is to destroy the volume, recreate it, reconfigure the shares, and restore the files from your backup.

Message 5 of 6
lpkvh08
Tutor

Re: Unable to erase inaccessible snapshots in ReadyNAS 424

OMG Finally!!! It works! All the snapshot allocation is cleared! Thank you so much! Now running a balance operation.

 

Here is the display from using # btrfs subvolume list -s /data

root@NAS:~# btrfs subvolume list -s /data
ID 35125 gen 128961 cgen 128961 top level 2635 otime 2019-04-06 19:00:14 path Applications/.snapshots/2317/snapshot
ID 35126 gen 226262 cgen 128962 top level 2977 otime 2019-04-06 19:00:15 path Backups/.snapshots/2317/snapshot
ID 35127 gen 128963 cgen 128963 top level 269 otime 2019-04-06 19:00:16 path Documents/.snapshots/2317/snapshot
ID 35128 gen 128964 cgen 128964 top level 2605 otime 2019-04-06 19:00:16 path Downloads/.snapshots/2317/snapshot
ID 35129 gen 128965 cgen 128965 top level 3777 otime 2019-04-06 19:00:16 path Games/.snapshots/2317/snapshot
ID 35130 gen 128966 cgen 128966 top level 268 otime 2019-04-06 19:00:17 path Music/.snapshots/2317/snapshot
ID 35131 gen 226262 cgen 128967 top level 266 otime 2019-04-06 19:00:17 path Pictures/.snapshots/2317/snapshot
ID 35132 gen 128968 cgen 128968 top level 4775 otime 2019-04-06 19:00:18 path resilio-sync/.snapshots/2317/snapshot
ID 35133 gen 226262 cgen 128969 top level 267 otime 2019-04-06 19:00:18 path Videos/.snapshots/2317/snapshot
ID 35845 gen 131074 cgen 131074 top level 2635 otime 2019-04-17 20:00:15 path Applications/.snapshots/2397/snapshot
ID 35846 gen 226262 cgen 131075 top level 2977 otime 2019-04-17 20:00:15 path Backups/.snapshots/2397/snapshot
ID 35847 gen 131076 cgen 131076 top level 269 otime 2019-04-17 20:00:16 path Documents/.snapshots/2397/snapshot
ID 35848 gen 131077 cgen 131077 top level 2605 otime 2019-04-17 20:00:16 path Downloads/.snapshots/2397/snapshot
ID 35849 gen 131078 cgen 131078 top level 3777 otime 2019-04-17 20:00:16 path Games/.snapshots/2397/snapshot
ID 35850 gen 131079 cgen 131079 top level 268 otime 2019-04-17 20:00:17 path Music/.snapshots/2397/snapshot
ID 35851 gen 226262 cgen 131080 top level 266 otime 2019-04-17 20:00:17 path Pictures/.snapshots/2397/snapshot
ID 35852 gen 131081 cgen 131081 top level 4775 otime 2019-04-17 20:00:18 path resilio-sync/.snapshots/2397/snapshot
ID 35853 gen 226262 cgen 131082 top level 267 otime 2019-04-17 20:00:18 path Videos/.snapshots/2397/snapshot

I opened another SSH terminal and started using # btrfs subvolume delete -c <path> and it went something like this,

root@NAS:~# btrfs subvolume delete -c /data/Applications/.snapshots/2317/snapshot
Delete subvolume (commit): '/data/Applications/.snapshots/2317/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Backups/.snapshots/2317/snapshot
Delete subvolume (commit): '/data/Backups/.snapshots/2317/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Documents/.snapshots/2317/snapshot
Delete subvolume (commit): '/data/Documents/.snapshots/2317/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Downloads/.snapshots/2317/snapshot
Delete subvolume (commit): '/data/Downloads/.snapshots/2317/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Games/.snapshots/2317/snapshot
Delete subvolume (commit): '/data/Games/.snapshots/2317/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Music/.snapshots/2317/snapshot
Delete subvolume (commit): '/data/Music/.snapshots/2317/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Pictures/.snapshots/2317/snapshot
Delete subvolume (commit): '/data/Pictures/.snapshots/2317/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/resilio-sync/.snapshots/2317/snapshot
Delete subvolume (commit): '/data/resilio-sync/.snapshots/2317/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Videos/.snapshots/2317/snapshot
Delete subvolume (commit): '/data/Videos/.snapshots/2317/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Applications/.snapshots/2397/snapshot
Delete subvolume (commit): '/data/Applications/.snapshots/2397/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Backups/.snapshots/2397/snapshot
Delete subvolume (commit): '/data/Backups/.snapshots/2397/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Documents/.snapshots/2397/snapshot
Delete subvolume (commit): '/data/Documents/.snapshots/2397/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Downloads/.snapshots/2397/snapshot
Delete subvolume (commit): '/data/Downloads/.snapshots/2397/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Games/.snapshots/2397/snapshot
Delete subvolume (commit): '/data/Games/.snapshots/2397/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Music/.snapshots/2397/snapshot
Delete subvolume (commit): '/data/Music/.snapshots/2397/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Pictures/.snapshots/2397/snapshot
Delete subvolume (commit): '/data/Pictures/.snapshots/2397/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/resilio-sync/.snapshots/2397/snapshot
Delete subvolume (commit): '/data/resilio-sync/.snapshots/2397/snapshot'
root@NAS:~# btrfs subvolume delete -c /data/Videos/.snapshots/2397/snapshot
Delete subvolume (commit): '/data/Videos/.snapshots/2397/snapshot'

And finally the snapshot allocation was cleared. I will post the web UI page screenshot again after completion of the Balance operation. Again thank you so much!

 

Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 1839 views
  • 0 kudos
  • 2 in conversation
Announcements