NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Windows SMB created folder undeletable
At one point I started creating folders in the root directory of my RN via Windows SMB instead of creating shares on the RN. I'm trying to delete one of those SMB folders that I created. It successfu...
nickjames wrote:
When I rerun that command, snapper list-config, all of the subvolumes shown match the GUI and Windows with the exception of NOT seeing Test123 in the SSH session.
My guess here is that you renamed the original share folder to Test123 from Windows. Then you deleted the share from the NAS admin UI. That would generate an error because the share folder no longer existed. But it appears to have deleted the share from the ReadyNAS database, and also deleted the snapshot configuration.
Before you can delete Test123, you need to delete all the snapshots that it has. If you had a snapper config, you could have deleted them as a group. But since you don't, they need to be deleted one at a time. From your earlier btrfs subvolume list /RAID50.6x2TB | grep -i Test123 we can see 83 snapshots that need to be deleted.
The first "real" snapshot in your older post has a path of Test123/.snapshots/10/snapshot
To manually delete that one, enter btrfs subvolume delete -c /RAID50.6x2TB/Test123/.snapshots/10/snapshot
It could take a while for the deletion to complete (not sure how long).
If it does complete with no error, proceed to the next one (/RAID50.6x2TB/Test123/.snapshots/41/snapshot. Continue until you delete them all (ending with /RAID50.6x2TB/Test123/.snapshots/1517/snapshot). Note if you use the up arrow key on the keyboard, you will see the previous command. You can then use the left and right arrows to position the cursor, and change the numeric value (10 to 41, etc until you get to 1517). That should reduce the amount of typing.
When they are all done, then enter btrfs subvolume delete -c /RAID50.6x2TB/Test123/.snapshots to delete the .snapshots folder and finally btrfs subvolume delete -c /RAID50.6x2TB/Test123/ to delete the share.
Because snapper list-configs grep command didn't produce any information, I was saying that I didn't know how to rerun that command but with a verbose switch to hopefully get more data.
When I rerun that command, snapper list-config, all of the subvolumes shown match the GUI and Windows with the exception of NOT seeing Test123 in the SSH session.
nickjames wrote:
When I rerun that command, snapper list-config, all of the subvolumes shown match the GUI and Windows with the exception of NOT seeing Test123 in the SSH session.
My guess here is that you renamed the original share folder to Test123 from Windows. Then you deleted the share from the NAS admin UI. That would generate an error because the share folder no longer existed. But it appears to have deleted the share from the ReadyNAS database, and also deleted the snapshot configuration.
Before you can delete Test123, you need to delete all the snapshots that it has. If you had a snapper config, you could have deleted them as a group. But since you don't, they need to be deleted one at a time. From your earlier btrfs subvolume list /RAID50.6x2TB | grep -i Test123 we can see 83 snapshots that need to be deleted.
The first "real" snapshot in your older post has a path of Test123/.snapshots/10/snapshot
To manually delete that one, enter btrfs subvolume delete -c /RAID50.6x2TB/Test123/.snapshots/10/snapshot
It could take a while for the deletion to complete (not sure how long).
If it does complete with no error, proceed to the next one (/RAID50.6x2TB/Test123/.snapshots/41/snapshot. Continue until you delete them all (ending with /RAID50.6x2TB/Test123/.snapshots/1517/snapshot). Note if you use the up arrow key on the keyboard, you will see the previous command. You can then use the left and right arrows to position the cursor, and change the numeric value (10 to 41, etc until you get to 1517). That should reduce the amount of typing.
When they are all done, then enter btrfs subvolume delete -c /RAID50.6x2TB/Test123/.snapshots to delete the .snapshots folder and finally btrfs subvolume delete -c /RAID50.6x2TB/Test123/ to delete the share.
As always, thank you, StephenB. We are lucky to have you on these forums!
That did the trick... until next time!
One last thing... clean up. I'll disable SSH and create a new user on the RN without administrator privilege's. Would you suggest that as a good practice so I don't get myself into this mess in the future?
nickjames wrote:
One last thing... clean up. I'll disable SSH and create a new user on the RN without administrator privilege's. Would you suggest that as a good practice so I don't get myself into this mess in the future?
Definitely a good idea to access the NAS over SMB w/o using admin credentials.
Disabling SSH is up to you - one benefit to leaving it on is that you can often use it to access the NAS when the web ui becomes non-responsive. If you disable it, then of course you need the web ui to re-enable.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
