I am using UFS drive storage, says its full but I have lots of space left.

  • If memory serves me correctly that is not the default setting, I wonder if it's possible to change that within the plugin as this seems to come up as a root cause of data distribution.

    Most Free Space is not the default. I've already broached this topic with ryecoaaron about changing it. Apparently there was a raging argument on which policy should be the default, back in the day, and all settled on Existing Path, most free space.


    (For readers of this thread)
    If using the most free space policy, one becomes (essentially) married to mergerfs. Files are evenly distributed among the drives in a RAID5 like manner which means that the mergerfs mount point must be used. Files and directory structure explode over all drives, as files are distributed according to most free space. To back out of mergerfs, folders and their files must be manually consolidated onto one drive which is complicated for a beginner.


    That's the benefit of Existing Path, most free space. Once the path is set on one drive, as in a new shared folder, all files go to that folder. If dropping the mount point, there's nothing to consolidate or sort out. Files are under their intended sub-directory. The problem with this policy is "Video" storage. When a "video" shared folder is set, using EP,MFS that folder is the only place where video is stored. This is what we see on the forum and it's the reason why the associated drive fills up.
    _________________________________________

    The only real solution I can think of is another doc, explaining these two policies to users and what implementing them would mean. Now that ryecoaaron has a Wiki, a plugin doc and a referring link in the plugin's frame might take care of the issue.

  • That's the benefit of Existing Path, most free space. Once the path is set on one drive, as in a new shared folder, all files go to that folder. If dropping the mount point, there's nothing to consolidate or sort out. Files are under their intended sub-directory. The problem with this policy is "Video" storage. When a "video" shared folder is set, using EP,MFS that folder is the only place where video is stored. This is what we see on the forum and it's the reason why the associated drive fills up.

    One way to solve it would be for OMV to automatically create the folder on the second disk when the first one is full. It would be a transparent process for the user maintaining the Existing Path, most free space policy.

    Core I3 3225, RAM 4GB, SnapRaid and UnionFS, 1 parity disk (5TB), 3 data disks (5TB+4TB+4TB), 1 x 32GB USB disk for startup, 1 x 60GB SSD disk for docker

    I DO NOT SPEAK ENGLISH. I translate with google, sorry if sometimes I am not well understood :)

  • One way to solve it would be for OMV to automatically create the folder on the second disk when the first one is full. It would be a transparent process for the user maintaining the Existing Path, most free space policy.

    This is not a good idea. It will defeat the purpose of choosing that policy to prevent exactly that from happening.


    I think a better solution would be for users to read the documentation for the software so that they can make informed decisions about create policies rather than reading the documentation later to find why it's not working for them as they expected.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 5.x on ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380 + Silverstone DS380 DAS Box.

  • most free space...Files and directory structure explode over all drives, as files are distributed according to most free space. To back out of mergerfs, folders and their files must be manually consolidated onto one drive which is complicated for a beginner.


    Existing Path, most free space...The problem with this policy is "Video" storage. When a "video" shared folder is set, using EP,MFS that folder is the only place where video is stored. This is what we see on the forum and it's the reason why the associated drive fills up.

    Everybody likes automation, but it is plain to see there is no fully automated "perfect" solution when using mergerfs (UnionFS.) Wouldn't a better (but more hands-on) solution be using individual disks and use the symlinks plugin? File paths in containers and plugins can use the symlink and when a video-type folder "explodes", just move it to a new dedicated drive and change the path for that symlink.


    I'm using the UFS plugin with most free space and imagining a snarled mess inside my two data drives concerns me. I don't like things where it's not easy "to back out of." Thankfully, I have a single-disk remote backup of my two pooled disks. :)

    Simple and sure backup and restore: In a Scheduled Job: rsync -av --delete /srv/dev-disk-by-label-SOURCE/ /srv/dev-disk-by-label-DESTINATION/ (HT: Getting Started with OMV5)
    OMV 5 (current) - Hardware: Thinkserver TS140, Nextcloud, Plex, Airsonic, Navidrome, Ubooquity, Digikam, & Heimdall - NanoPi M4 (v.1), backup - Odroid XU4, Pi-Hole (DietPi) - Testing/Playing: hc2, xu4, Pi 3B+, Odroid H2. Mac user trying to convert to Linux on a HP dx2400, Debian 10 XFCE.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!