0
Turns out that my NAS QNAP had a disk failure, ending in the Filesystem clean with errors. I have little to no experience dealing with recovering failed filesystems.
I have been running e2fsck_64 and repairing everything waiting very long times (4 days and still shows around806 inodes containing multiply-claimed blocks) however since 2 days ago everything that e2fsck_64 is verifying are files stored at the @Recycle directory. Are files that I do not want to keep at all.
By default the e2fsck_64 version does automatically repairs everything. I thought to find a way to free the sectors / inodes corresponding to everything on the @Recycle directories to speed up the process.
Is this going to mess even the Filesystem? is it fine to run?
The second part is that I have not succeeded in removing directories nor files using:
# debugfs -w /dev/mapper/cachedev1
# debugfs: rmdir /Contents/@Recycle
# rmdir: directory not empty
Or alternatively I get
# debugfs: rm /Contents/@Recycle/file.extension
# rm: File not found by ext2_lookup while trying to solve filename
Could you please guide me on how to remove everything on @Recycle to speedup the e2fsck_64 Filesystem recovery? (Or is it really a bad idea)
maynaoj
Posted 2019-08-04T13:11:12.253
Reputation: 1