Mitchell Deoudes

My array contains a lot of very old data from many different sources, and as a result, I've got a ton of (1.5 million) files with zero sub-second timestamps. It's never been much of an issue, since I don't move important files around much: They live where they live, and the only time they move is a whole-disk copy (which preserves the directory structure, and thus doesn't need sub-second timestamps, I believe). But today I needed to move some zero-sub files to another disk (different directory),...

Aha - so I found the original source of the problem: there was an excel file that produced a "Unexpected data modification of a file without parity!" warning message in a sync run from several days ago that I had missed. I'm assuming that the file contents were changed without changing the mtime, when it was opened for reading by excel, making it no longer match to another copy of the file elsewhere in the array. The sync run says as much: This file was detected as a copy of another file with the...

Yep - as expected, running snapraid fix -e resulted in nothing to do: Self test... Loading state from /var/snapraid.content... Searching disk d2... Searching disk d3... Searching disk d4... Selecting... Using 3212 MiB of memory for the file-system. Initializing... Selecting... Fixing... Nothing to do Everything OK So while I'm still not happy about seeing "WARNING! Unexpected file errors!", I'm not sure there's any more I can do to figure out what happened. I suppose I could run a full "snapraid...

Apologies if this is a stupid question, but I've been using snapraid forever with almost no errors. Primarily, I've seen the excel-touching-file-contents-without-updating-the-timestamp problem, and periodically the zero-file-size problem for things like mailboxes that get emptied. So, practically no genuine file errors. I have an overnight script that runs a sync, and then a scrub of 8% of the array. Last night, it gave the following "WARNING! Unexpected file errors!" message, but snapraid didn't...

Apologies if this is a stupid question, but I've been using snapraid forever with almost no errors. Primarily, I've seen the excel-touching-file-contents-without-updating-the-timestamp problem, and periodically the zero-file-size problem for things like mailboxes that get emptied. So, practically no genuine file errors. I have an overnight script that runs a sync, and then a scrub of 8% of the array. Last night, it gave the following "WARNING! Unexpected file errors!" message, but snapraid didn't...

Apologies if this is a stupid question, but I've been using snapraid forever with almost no errors. Primarily, I've seen the excel-touching-file-contents-without-updating-the-timestamp problem, and periodically the zero-file-size problem for things like mailboxes that get emptied. So, practically no genuine file errors. I have an overnight script that runs a sync, and then a scrub of 8% of the array. Last night, it gave the following "WARNING! Unexpected file errors!" message, but snapraid didn't...

I've got a few mail (mbox) files that I rotate at year end - moving them to an archive, and re-creating them as empty for the new year. In my year-end notes, I have a warning to myself saying "use 'touch' to create the empty files with new dates, so that snapraid won't see them as suddenly zero size". This year, I did the usual thing, and created three new empty files for these three mboxes, using 'touch' to ensure a current date. But the subsequent snapraid sync run reported them as zero size, and...

I've got an array with a variety of different disk sizes. The parity disks are the largest - meaning that they are about 40% empty. I also use a 200GB swap file on my (linux) system, mostly because when snapraid sync runs overnight, it will sometimes force the system to swap, if a bunch of other programs are open. (I try not to let this happen, but it's a backup so that there's not a total failure.) Right now, the swap file is located on one of my data disks. Is there any reason not to move the swap...