Jump to content
Covecube Inc.

Craig

Members
  • Content Count

    3
  • Joined

  • Last visited

  1. Thanks to the service log I've spotted that renaming a duplicated file appears to make drivepool check the entire pool. Is that the expected behaviour? (I probably do this at least once a day, which is why I must see it checking so often.)
  2. I'll report back when I've had time to look at all the options, but wanted to say thank you now for both the replies.
  3. I'm a big fan of DrivePool, and recently moved a load of pooled drives to a new computer and it just worked, so that was brilliant. Just getting that out there so you know I'm not moaning for the sake of it! However, I'd really like to know more about why DrivePool is doing certain things. My system seems to re-measure a lot. To resolve this I've slowly replaced cables, drives, controllers, and now the whole computer (not just for DrivePool, but I had hoped it would help.) I probably do have a dodgy disk, but I can't afford to replace the whole lot, and it's not obvious which one is suspect. (I do also have scanner, 3 drives have minor smart problems, but otherwise healthy.) So would it be possible to find out what triggered a measure? If it thinks a drive disappeared for a second, can I find that in a log, or could it be exposed in the UI better? A bonus question: could DrivePool tell us what files it thinks are open? A few months ago I'd always have a baseline 20+ files open (as reported in the UI), with no pool activity. I replaced an old drive and the files open dropped to 10, which made me wonder is having persistent files open another symptom of an underlying disk issue? Thanks!
×
×
  • Create New...