"...both folders shared with the samba service..." was my missing step (d**n!).
Now that I have the MergerFS-pool and the three hdds shared successfully I have two directories "HDD" and "TEST" I created in the MergerFS-Share but I can't find these directories on none of the dedicated hdds.
There's something I'm doing wrong. I've shared all 3 hdds but can't see them on my Win-client.
I can access the MergerFS-pool though but the three new Shares are not displayed on the client.
Thanks a lot for your reply.
So adding an additional Share for every hdd of the MergerFS-pool should enable me to copy files between desired hdds including adding directories where I want them to be added.
Hello,
I've set up MergerFS successfully and now having some questions:
(1) How can I move any files from one particular hdd (which I want to use as parity-hdd in SnapRAID later on) of my MergerFS pool consisting of 3 hdds?
(2) How can I remove this hdd from my MergerFS-pool?
(3) When creating new directories on the Share (MergerFS-pool) on which drive(s) exactly are these directories? Both hdds, just one, which?
(4) If I want to build a new directory just on a particular/single hdd from my MergerFS-pool how can I do this?
(5) What exactly happens when a directory exists on just one hdd of the MergerFS-pool and space is running out while copying files to this directory?
Thanks a lot for helping.
Edit: After formatting the two new drives with EXT4 I could select them both in the MergerFS-Pool and after restarting ist I now have 12TB (3x4TB) disk space on the MergerFS.
I added two disks and deleted them. I can't add them to the existing mergerfs pool.
Thank you.
I did exactly what is described in your link and failed in my first try.
Now I did everything again, only difference was using just one hdd.
Everything seems to be OK right now and I can access the SMB-share via Wind 10 client.
What I didn't find is an option in mergerfs to add another hdd to an existing mergerfs-pool. Because this exactly is the usecase with mergerfs I missed something in the options I guess.
When creating mergerfs I get:
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color mergerfs 2>&1' with exit code '1': debian:
----------
ID: configure_pool_dir
Function: file.directory
Name: /srv/mergerfs
Result: True
Comment: The directory /srv/mergerfs is in the correct state
Started: 12:14:06.401157
Duration: 3.953 ms
Changes:
----------
ID: remove_mergerfs_mount_files_/etc/systemd/system
Function: module.run
Result: True
Comment: file.find: ['/etc/systemd/system/srv-mergerfs-MERGER\\x2d01.mount']
Started: 12:14:06.405531
Duration: 2.032 ms
Changes:
----------
file.find:
- /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount
----------
ID: systemd_remove_dead_symlinks
Function: cmd.run
Name: find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete
Result: True
Comment: Command "find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete" run
Started: 12:14:06.407967
Duration: 4.288 ms
Changes:
----------
pid:
6299
retcode:
0
stderr:
stdout:
/etc/systemd/system/multi-user.target.wants/srv-mergerfs-MERGER\x2d01.mount
----------
ID: configure_mergerfs_MERGER-01
Function: file.managed
Name: /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount
Result: True
Comment: File /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount updated
Started: 12:14:06.412440
Duration: 37.136 ms
Changes:
----------
diff:
New file
mode:
0644
----------
ID: systemd-reload_MERGER-01
Function: cmd.run
Name: systemctl daemon-reload
Result: True
Comment: Command "systemctl daemon-reload" run
Started: 12:14:06.449722
Duration: 163.649 ms
Changes:
----------
pid:
6306
retcode:
0
stderr:
stdout:
----------
ID: enable_MERGER-01_mergerfs
Function: service.enabled
Name: srv-mergerfs-MERGER\x2d01.mount
Result: True
Comment: Service srv-mergerfs-MERGER\x2d01.mount has been enabled, and is in the desired state
Started: 12:14:06.632960
Duration: 327.67 ms
Changes:
----------
srv-mergerfs-MERGER\x2d01.mount:
True
----------
ID: restart_MERGER-01_mergerfs
Function: cmd.run
Name: systemctl restart srv-mergerfs-MERGER\x2d01.mount
Result: False
Comment: Command "systemctl restart srv-mergerfs-MERGER\x2d01.mount" run
Started: 12:14:06.960897
Duration: 7.615 ms
Changes:
----------
pid:
6356
retcode:
5
stderr:
Failed to restart srv-mergerfs-MERGERx2d01.mount: Unit srv-mergerfs-MERGERx2d01.mount not found.
stdout:
Summary for debian
------------
Succeeded: 6 (changed=6)
Failed: 1
------------
Total states run: 7
Total run time: 546.343 ms
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color mergerfs 2>&1' with exit code '1': debian:
----------
ID: configure_pool_dir
Function: file.directory
Name: /srv/mergerfs
Result: True
Comment: The directory /srv/mergerfs is in the correct state
Started: 12:14:06.401157
Duration: 3.953 ms
Changes:
----------
ID: remove_mergerfs_mount_files_/etc/systemd/system
Function: module.run
Result: True
Comment: file.find: ['/etc/systemd/system/srv-mergerfs-MERGER\\x2d01.mount']
Started: 12:14:06.405531
Duration: 2.032 ms
Changes:
----------
file.find:
- /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount
----------
ID: systemd_remove_dead_symlinks
Function: cmd.run
Name: find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete
Result: True
Comment: Command "find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete" run
Started: 12:14:06.407967
Duration: 4.288 ms
Changes:
----------
pid:
6299
retcode:
0
stderr:
stdout:
/etc/systemd/system/multi-user.target.wants/srv-mergerfs-MERGER\x2d01.mount
----------
ID: configure_mergerfs_MERGER-01
Function: file.managed
Name: /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount
Result: True
Comment: File /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount updated
Started: 12:14:06.412440
Duration: 37.136 ms
Changes:
----------
diff:
New file
mode:
0644
----------
ID: systemd-reload_MERGER-01
Function: cmd.run
Name: systemctl daemon-reload
Result: True
Comment: Command "systemctl daemon-reload" run
Started: 12:14:06.449722
Duration: 163.649 ms
Changes:
----------
pid:
6306
retcode:
0
stderr:
stdout:
----------
ID: enable_MERGER-01_mergerfs
Function: service.enabled
Name: srv-mergerfs-MERGER\x2d01.mount
Result: True
Comment: Service srv-mergerfs-MERGER\x2d01.mount has been enabled, and is in the desired state
Started: 12:14:06.632960
Duration: 327.67 ms
Changes:
----------
srv-mergerfs-MERGER\x2d01.mount:
True
----------
ID: restart_MERGER-01_mergerfs
Function: cmd.run
Name: systemctl restart srv-mergerfs-MERGER\x2d01.mount
Result: False
Comment: Command "systemctl restart srv-mergerfs-MERGER\x2d01.mount" run
Started: 12:14:06.960897
Duration: 7.615 ms
Changes:
----------
pid:
6356
retcode:
5
stderr:
Failed to restart srv-mergerfs-MERGERx2d01.mount: Unit srv-mergerfs-MERGERx2d01.mount not found.
stdout:
Summary for debian
------------
Succeeded: 6 (changed=6)
Failed: 1
------------
Total states run: 7
Total run time: 546.343 ms in /usr/share/php/openmediavault/system/process.inc:197
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(170): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatushx...', '/tmp/bgoutputaH...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(192): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}
I configured OMV 6.3.12 with mergerfs successfully but got a lot of "connection Lost" errors.
Is this a well known behaviour of OMV 6 or what else could be the problem?
Never had any problems in my 1GB-home-Network.
The hdds are from a older NAS-system.
A USB3-Stick is used for OMV6.
Thanks a lot. I'll give SnapRAID a try.
Back again to mergerfs: When I want to have just one share spaning over for example 3 hdds then I should use mergerfs.
Am I right that if one of these 3 hdds fails just the files from this one hdd are lost/missing in the share but access to the remaining files/hdds is possible without problems?
If I later change my mind and want a RAID-5 there ist no solution to add an additional disk and keep the data of my 3-hdd-share?
When did I say that?
You need parity to avoid bitrot, therefore you need some kind of Raid.
Now we're in sync again, thanks.
In my opinion any kind of Raid is not necessary for a standard home system.
If the information is valuable and is going to be stored for a long time, perhaps avoiding bitrot could be the only reason. For that you can use ZFS, BTRFS or snapraid.
So ZFS, BTRFS or SnapRaid without RAID will avoid bitrot?
Very interesting perspective and without RAID not all hdds need to spin up (?).
Thanks chente.
So what are the advantages/pro's of ZFS for home-use over the other more convenient filesystems OMV offers?
Are there any to take in account?
Am I correct that ZFS without RAID pools hdds and in case of a hardware failure only the files of this defective hdd are lost?
With ZFS-Z1 this won't happen because one hdd can fail without loosing data.
And what if ransomware hit your system? raid isn't backup. You would be better off to backup one drive to another.
I know. My important files are backed up on another NAS, USB-HDD and enrypted in the cloud 
Any reason why you need raid?
Just for not loosing my data if one disk fails in the RAID.
I have some experience with OMV 4 and 5.
Now I want to install a completely new NAS mith OMV6, using ZFS-1 (RAID 5).
Now I have some questions:
-is 8GB RAM enough with a Intel I7 CPU?
-can I start with just one ore two hdds and ZFS (without RAID) and later change to ZFS-1 without loosing data
Thanks a lot for helping.
What exactly should help me with your given URL?
I think I didn't get the point.
Hi,
I started my paperless-ngx journey last weekend with the docker image provided by linuxserver.
So far so good but unfortunately no pdf saved in the consume folder is processed and the OCR-language is englisch.
After reading the documentation I found docker-compose.env and wanted to set some environment variable but paperless-ngx seems to ignore the .env file completely.
My docker-compose.yml:
version: "2.1"
services:
paperless-ngx:
image: lscr.io/linuxserver/paperless-ngx:latest
container_name: paperless-ngx
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Berlin
volumes:
- /home/john/docker/paperless-ngx:/config
- /mnt/nas/paperless-ngx:/data
ports:
- 8601:8000
restart: unless-stoppedand my docker-compose.env:
PAPERLESS_OCR_LANGUAGE=deu+eng
PAPERLESS_CONSUMER_POLLING=60Thanks y lot for helping me out again.