RN314 - cannot delete file / folder - file system error?

Question

Hello community&nbsp;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.&nbsp; This seemed to have processed ok for most of the files, but after the delete was complete (per windows), I noticed that the folder still existed.&nbsp; On examination I could see that there was a file left over that was causing some sort of file error - see attached weird error message when browsing the share from a web browser.&nbsp; Nothing I do can get rid of this file.&nbsp; I have restarted the NAS, and I have performed a disk test.&nbsp; Neither helped, although I'm not sure if the disk test returned any errors because this does not seem to get logged.&nbsp; I should also point out that a backup job, that I had forgot to disable, that usually copies the contents of this folder onto an external hard drive, failed and put the system into read only mode (which i fixed with a reboot)&nbsp;How do I run a file &amp; directory system test on the NAS to try and cleanup what is clearly a failure in the file system integrity?&nbsp;ThanksMark

StephenB · Answer

Did you download the log zip file, and look in there for errors?
&nbsp;
Generally a backup job failure wouldn't put the NAS into a read-only state.&nbsp; It sounds like something more serious went wrong with the file system (perhaps while the backup job was running).&nbsp; Rebooting when it goes read-only was a bit risky - there are cases where the volume isn't mountable at all when you do that.
&nbsp;
You can send a PM to one of the mods ( JohnCM_S&nbsp;or Marc_V&nbsp;), and ask them to analyze your log zip.&nbsp; Include a downloadable link to the zip in the private message.&nbsp; You send/receive PMs using the envelope icon in the upper right of the forum page.
&nbsp;
If you use the NAS for primary storage, you should also make sure your backup is up to date, as you might need to destory the volume and recreate it from scratch.
&nbsp;

MarkC_za · Answer

Hi StephenB, thanks, I suspected I would have to recreate the volume from scratch.&nbsp; I was hoping for some miracle chkdsk function like in NTFS file sysyems.&nbsp; 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*.&nbsp;This happens about every 2 years with my setup.&nbsp; Its so frustrating.

StephenB · Answer

If the problem is only in the specific subvolume, you could potentially delete the share, and recreate it.&nbsp;
&nbsp;
Then perhaps try some of the options here to look for issues:&nbsp;https://btrfs.wiki.kernel.org/index.php/Btrfsck
&nbsp;

MarkC_za · Answer

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).&nbsp; Something in the file system went really bad, I wish I knew why but I suppose it's just one of those bugs.&nbsp; 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.&nbsp; This bug they fixed in their next OS release.&nbsp; 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! "&nbsp;Thans for your help StephenMark

StephenB · Answer

MarkC_za&nbsp;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.&nbsp;

Bad things can happen when a BTRFS volume gets too full.&nbsp; 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.&nbsp; So if you are using those, I suggest switching to "custom" snapshots where you have explicit control over snapshot retention.&nbsp; There is no pruning, but&nbsp; option to make snapshots only when there have been changes works just as well (actually better) for me.
&nbsp;
MarkC_za&nbsp;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! "
&nbsp;

I'd also at least look at the disk health (disk_info.log).&nbsp; if SSH is enabled, try using smartctl -x - that reports cached errors that aren't in the log.&nbsp; I found one failed disk that way that still had good smart stats.&nbsp; &nbsp;Maybe also test them in a Windows PC using vendor tools (Seatools for Seagate; Lifeguard for Western Digital).

Forum Discussion

RN314 - cannot delete file / folder - file system error?

5 Replies

Related Content

Delete folder starting with double backslash

Deleted folder log

Deleting access to a CBR750

Recovering Accidently Deleted Folder

Deleting old home folders

NETGEAR Academy

ProSupport for Business