March 11, 20188 yr I have 3 files on my cache drive which will not delete. I stopped the array and ran a check on the (3 month old) cache drive and got this: checking extents checking free space cache checking fs roots root 5 inode 795665 errors 200, dir isize wrong root 5 inode 7350789 errors 1, no inode item unresolved ref dir 795665 index 41031 namelen 12 name nzbdrone.pid filetype 1 errors 5, no dir item, no inode ref root 5 inode 7351526 errors 200, dir isize wrong root 5 inode 7767099 errors 1, no inode item unresolved ref dir 7351526 index 11728 namelen 15 name nzbdrone.db-wal filetype 1 errors 5, no dir item, no inode ref root 5 inode 7767100 errors 1, no inode item unresolved ref dir 7351526 index 11729 namelen 15 name nzbdrone.db-shm filetype 1 errors 5, no dir item, no inode ref Checking filesystem on /dev/sdf1 UUID: 26b1367d-fbda-42ef-98e1-34189018efd9 found 233614036992 bytes used err is 1 total csum bytes: 194593428 total tree bytes: 943652864 total fs tree bytes: 593100800 total extent tree bytes: 106102784 btree space waste bytes: 185965020 file data blocks allocated: 1768305549312 referenced 220438290432 What should I do now? Also, I cannot delete these three files mentioned and they show up with a ? in owner, group, and permissions. The disk mounts and everything seems to be fine except for this. tower-diagnostics-20180311-1949.zip Edited March 12, 20188 yr by mikedpitt420
March 12, 20188 yr Community Expert 10 hours ago, mikedpitt420 said: I stopped the array and ran a check Was the check repair or read only? If read only run repair but backup your cache first, if repair can't fix it, backup your cache, reformat and restore the data.
March 12, 20188 yr Author Thanks! --repair did the trick. I wonder why only that docker was creating this issue. Mike
March 13, 20188 yr 2 hours ago, mikedpitt420 said: Thanks! --repair did the trick. I wonder why only that docker was creating this issue. Mike Maybe the only part that got corrupted was the part occupied by that container? Much like any other filesystem I guess.
March 13, 20188 yr When a file system has broken files, it's normally files that are regularly modified.
Archived
This topic is now archived and is closed to further replies.