Keexrean Posted January 20, 2020 Share Posted January 20, 2020 I already "knew" what it was, I stated it before, but still I was curious to see 1> if I had files/folders with the same "defect" 2> eventually tell you what I knew about these files as for why they might have this issue (at least for me). Thinking about it, you might have a bitrot issue creeping under, depending of your file system But yeah, the issue with the dir command stalling is just linked to insuffiscent access right issues, else because it's a folder I prefer to keep unreachable from the network, else because it's locked by a docker running on it. Quote Link to comment
falconexe Posted January 20, 2020 Author Share Posted January 20, 2020 1 minute ago, Keexrean said: have a bitrot issue creeping under, depending of your file system I've been using the "Integrity" plugin for over a year. No bit rot yet... Quote Link to comment
Keexrean Posted January 20, 2020 Share Posted January 20, 2020 (edited) Then, that out of the question (which would have been concerning), I could be any combinaison of pesky users moving files around, killed/crashed >cp or >mv or other file operations, or just a buggy piece of software crapping out on files. Edited January 20, 2020 by Keexrean Quote Link to comment
falconexe Posted January 20, 2020 Author Share Posted January 20, 2020 (edited) I have updated my ALL Disk scripts. There are 2 copies attached. One does not suppress errors, and the other one does. Updates: Audit Timestamps Now in YYYY-MM-DD Format Was YYYY-DD-MM in Error Before Output Results Folder Now in YYYY-MM-DD Format (With Dashes) Was in YYYYMMDD Format Before (Without Dashes) UNRAID_Audit_All_Disks_NullErrors.bat UNRAID_Audit_All_Disks.bat Edited January 20, 2020 by falconexe Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.