Jump to content

JonathanM

Moderators
  • Posts

    16,212
  • Joined

  • Last visited

  • Days Won

    65

Posts posted by JonathanM

  1. 39 minutes ago, stainless_steve said:

    I am at 80% (737GB)

    80% is about 16GB, not 737GB

    On 4/15/2024 at 3:22 PM, stainless_steve said:

    I checked and the docker.img file is just 21.5GB big

     

    20 hours ago, JonathanM said:

    It's the percentage of space used INSIDE the docker.img file. Not the free space on the drive holding the image file.

     

  2. 14 hours ago, asbath said:

    This I believe will tell the system I want to move everything in appdata from the array to the cache.

    Everything will only be files not in use, so to get "everything" moved you need to stop the docker and vm services in settings. You will know when the services are stopped because the docker and vm tabs will be missing from the GUI.

  3. 6 hours ago, stainless_steve said:

    Where is the maximum size of 128GB coming from?

    Motherboard reported, may be accurate, maybe not.

     

    6 hours ago, stainless_steve said:

    what determines the maximum size of the Log ?

    fixed allocation by Unraid

     

    6 hours ago, stainless_steve said:

    and most importantly: why is the docker at 79% (732GB)? I checked and the docker.img file is just 21.5GB

    It's the percentage of space used INSIDE the docker.img file. Not the free space on the drive holding the image file.

  4. 39 minutes ago, asbath said:

    So I figured, easy enough, I'll just use cp to manually bring the files over from /mnt/user/appdata/* to /mnt/cache/appdata/*. That went swimmingly.

    Pretty sure that didn't work like you thought it did, because those locations are the same.

     

    /mnt/user paths are the combined view of all the root paths on the array disks and the pools combined. user share and disk share should never be mixed in a file operation.

  5. On 4/14/2024 at 8:50 AM, ConnerVT said:

    apcupsd may have this functionality as well,

    It does, I use it extensively, each of my VM's runs apcupsd in slave mode, and is set to begin shutting down a minute or two after the host server reports a loss of power. Server shutdown is much smoother for me if the VM's are all shut down before the server itself starts the shutdown sequence.

    • Thanks 1
  6. I just thought of a another VERY good reason I want the parity drive to be read all the way to the end.

     

    Hidden errors. Unless you run a complete SMART test, that portion of the parity drive beyond the last data drive is NEVER read or written during normal use. The last thing I want is for there to be a bad sector lurking in the last bit of the parity drive, just waiting for me to add a data drive and start exercising it. At least with a parity check that portion of the drive is read regularly.

     

    Count me as 1 vote to keep the current behaviour, for the above reason alone.

  7. 22 hours ago, thatdude78 said:

    The issue is my back up is a year old. During this period i replaced a failed 3TB HDD with an 18TB HDD plus I also had two parities when this backup was created which my current config did not.

    Just be glad that one of your current data drives wasn't in use as a parity with that old backup. That sort of error is generally fatal to the data that was on said drive.

     

    Lesson here, keep current backups, and delete any old backups made before a drive change. You really don't want to accidentally use an old backup.

  8. 16 hours ago, Gragorg said:

    I agree it should skip the portion after the largest data drive. 

    If that were implemented, it would require a change in the drive addition and replacement code, because it would no longer be a given that the full capacity of the parity drive is indeed zeroes. I don't see that kind of code rewrite happening, mainly because what is there now works, and mucking around with such important code that is currently working would require a VERY strong reason, given the amount of work needed to test for edge cases and general bugs that could be introduced.

    • Upvote 1
  9. 2 minutes ago, VanGoghComplex said:

    my server can also come back on automatically after restoration of of the UPS

    I strongly recommend not doing this. There are many reasons, but the most important in my mind is the need to evaluate the entire situation before allowing the server to come back up. If you are not on site to make that evaluation, there very well may be circumstances that you are not aware.

×
×
  • Create New...