Jump to content
Covecube Inc.

Lollaskates

Members
  • Content Count

    2
  • Joined

  • Last visited

  1. I believe the default is to just throw a write error (out of space), but I imagine there's an alternative way to handle it. More here: https://github.com/trapexit/mergerfs#policy-descriptions "If all branches are filtered an error will be returned. Typically EROFS (read-only filesystem) or ENOSPC (no space left on device) depending on the most recent reason for filtering a branch. ENOENT will be returned if no elegible branch is found." I may look into writing a balancer plugin if its possible with the current framework. Thanks for the response! I hope it does get implemented. If I w
  2. I saw that this was requested as early as 4 years ago and im not sure if it ever got traction. As you would expect I'm asking this question coming from a place of media storage. I intend on having SnapRaid underneath DrivePool to handle my fault tolerance, but Im looking to place files intelligently to minimally spin up drives when files are accessed. This is accomplished with MergerFS in linux by specifying epmfs as the default policy (of all drives where the path exists, choose drive with most available free space). Drive1: A:\Media\Movies\TheFirstMovie (2020)\ Drive2: B:\Media\M
×
×
  • Create New...