NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MarkC_za
Nov 10, 2019Aspirant
RN314 - cannot delete file / folder - file system error?
Hello community Using windows explorer and linked to my NAS via a mapped drive, I tried to delete a folder that contained a large number of backup files. This seemed to have processed ok for mos...
MarkC_za
Nov 11, 2019Aspirant
Hi StephenB, thanks, I suspected I would have to recreate the volume from scratch. I was hoping for some miracle chkdsk function like in NTFS file sysyems. Fortunately I have readyDR snapshots as well as external HD backups so no data will be lost, but oh the agony of starting from scratch, all the settings, backup jobs, plex servers, etc. *sigh*. This happens about every 2 years with my setup. Its so frustrating.
StephenB
Nov 11, 2019Guru - Experienced User
If the problem is only in the specific subvolume, you could potentially delete the share, and recreate it.
Then perhaps try some of the options here to look for issues: https://btrfs.wiki.kernel.org/index.php/Btrfsck
- MarkC_zaNov 12, 2019Aspirant
just today a second share also started giving me "source does not exist" errors, so I've taken the plunge and busy reseting the unit to factory default (30.84% complete after 2 hours... sigh). Something in the file system went really bad, I wish I knew why but I suppose it's just one of those bugs. The last time I had to restore from scratch, my unit was new enough for some support, and together we traced the bug to snapshots that were getting to big because the OS was not purging properly. This bug they fixed in their next OS release. Anyway, chalk this solution up to "It looks really bad, you do have backups right? 'Cause you gonna have to rebuild the volume from sratch! "
Thans for your help Stephen
Mark
- StephenBNov 13, 2019Guru - Experienced User
MarkC_za wrote:
The last time I had to restore from scratch, my unit was new enough for some support, and together we traced the bug to snapshots that were getting to big because the OS was not purging properly.
Bad things can happen when a BTRFS volume gets too full. If you are using the "smart" snapshots, then unfortunately the monthly ones are retained indefinitely, and eventually the volume will reach the threshold where the OS purges them to protect the file system. So if you are using those, I suggest switching to "custom" snapshots where you have explicit control over snapshot retention. There is no pruning, but option to make snapshots only when there have been changes works just as well (actually better) for me.
MarkC_za wrote:
Anyway, chalk this solution up to "It looks really bad, you do have backups right? 'Cause you gonna have to rebuild the volume from scratch! "
I'd also at least look at the disk health (disk_info.log). if SSH is enabled, try using smartctl -x - that reports cached errors that aren't in the log. I found one failed disk that way that still had good smart stats. Maybe also test them in a Windows PC using vendor tools (Seatools for Seagate; Lifeguard for Western Digital).
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!