ryanborstelmann

Oh my i can't believe myself! 😬 Thanks!

How can I run "zfs status -x" to see the status of the pool(s)? I swear this worked at one point, but now it throws an error that it doesn't know what "status" is as a command: root@NAS01:~# zfs status -x unrecognized command 'status' usage: zfs command args ... where 'command' is one of the following: create [-p] [-o property=value] ... <filesystem> create [-ps] [-b blocksize] [-o property=value] ... -V <size> <volume> destroy [-fnpRrv] <filesystem|volume> destroy [-dnpRrv] <filesystem|volume>@<snap>[%<snap>][,...] destroy <filesystem|volume>#<bookmark> snapshot|snap [-r] [-o property=value] ... <filesystem|volume>@<snap> ... rollback [-rRf] <snapshot> clone [-p] [-o property=value] ... <snapshot> <filesystem|volume> promote <clone-filesystem> rename [-f] <filesystem|volume|snapshot> <filesystem|volume|snapshot> rename [-f] -p <filesystem|volume> <filesystem|volume> rename -r <snapshot> <snapshot> bookmark <snapshot> <bookmark> list [-Hp] [-r|-d max] [-o property[,...]] [-s property]... [-S property]... [-t type[,...]] [filesystem|volume|snapshot] ... set <property=value> ... <filesystem|volume|snapshot> ... get [-rHp] [-d max] [-o "all" | field[,...]] [-t type[,...]] [-s source[,...]] <"all" | property[,...]> [filesystem|volume|snapshot|bookmark] ... inherit [-rS] <property> <filesystem|volume|snapshot> ... upgrade [-v] upgrade [-r] [-V version] <-a | filesystem ...> userspace [-Hinp] [-o field[,...]] [-s field] ... [-S field] ... [-t type[,...]] <filesystem|snapshot> groupspace [-Hinp] [-o field[,...]] [-s field] ... [-S field] ... [-t type[,...]] <filesystem|snapshot> mount mount [-vO] [-o opts] <-a | filesystem> unmount [-f] <-a | filesystem|mountpoint> share <-a [nfs|smb] | filesystem> unshare <-a [nfs|smb] | filesystem|mountpoint> send [-DnPpRvLec] [-[i|I] snapshot] <snapshot> send [-Lec] [-i snapshot|bookmark] <filesystem|volume|snapshot> send [-nvPe] -t <receive_resume_token> receive [-vnsFu] [-o <property>=<value>] ... [-x <property>] ... <filesystem|volume|snapshot> receive [-vnsFu] [-o <property>=<value>] ... [-x <property>] ... [-d | -e] <filesystem> receive -A <filesystem|volume> allow <filesystem|volume> allow [-ldug] <"everyone"|user|group>[,...] <perm|@setname>[,...] <filesystem|volume> allow [-ld] -e <perm|@setname>[,...] <filesystem|volume> allow -c <perm|@setname>[,...] <filesystem|volume> allow -s @setname <perm|@setname>[,...] <filesystem|volume> unallow [-rldug] <"everyone"|user|group>[,...] [<perm|@setname>[,...]] <filesystem|volume> unallow [-rld] -e [<perm|@setname>[,...]] <filesystem|volume> unallow [-r] -c [<perm|@setname>[,...]] <filesystem|volume> unallow [-r] -s @setname [<perm|@setname>[,...]] <filesystem|volume> hold [-r] <tag> <snapshot> ... holds [-r] <snapshot> ... release [-r] <tag> <snapshot> ... diff [-FHt] <snapshot> [snapshot|filesystem] Each dataset is of the form: pool/[dataset/]*dataset[@name] For the property list, run: zfs set|get For the delegated permission list, run: zfs allow|unallow Thanks!

Feature question - I'm looking to run a script while CA Backup & Restore has my VMs stopped - I'd like to run a Plex database maintenance script that must run when Plex is stopped, so ideally my nightly CA Backup would be the best option. I know based on the comment by @Squid (see below) that the custom scripts in CA Backup/Restore run prior to the containers stopping, and after the containers start - nothing that can run while the containers are stopped. Is that the case? Any way I can do what I'm looking for? I suppose I could do a custom stop script (prior to containers stopping) that has "docker stop plex" at the start of the script, then backup/restore will start the Plex container after the backup is complete? Will that work?

I was able to resolve it by running chmod 777 /mnt/docker/* Unsure why this works while the /mnt/user/docker one has all the non-777 perms, but that's fine. I should probably someday go back and find out what's going on, but for my Plex server, it doesn't matter that things are 777. Thanks!

No dice set it to /mnt/docker as my ZFS mountpoint, and I still get permissions issues. Here's my zpool setup and transfer of CA Backup to the new pool - maybe something I need to add/change in this? I stop docker prior to the configuration, change where my docker.img file is located in unraid settings, then start it up after the process. zpool create docker -m /mnt/docker mirror scsi-350000393a819195c scsi-350000393a8195a74 mirror scsi-350000393b82b5d94 scsi-350000393b82b6a2c zfs set compression=lz4 docker zfs set atime=off docker tar xzvf /mnt/user/backups/docker/2018-09-12\@03.01/CA_backup.tar.gz -C /mnt/docker/ cp /mnt/user/docker/docker.img /mnt/docker/

Trying this out. Will report back findings. Thanks!

Hey all, anything I should be aware of regarding folder permissions when using ZFS on UnRAID? I've moved my docker's appdata folder from /mnt/user/docker to /zfs/docker (using the ZFS plugin to create a zpool outside my array): root@NAS01:~# zfs list NAME USED AVAIL REFER MOUNTPOINT docker 20.1G 518G 20.1G /zfs/docker root@NAS01:~# zpool status pool: docker state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM docker ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 scsi-350000393a819195c ONLINE 0 0 0 scsi-350000393a8195a74 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 scsi-350000393b82b5d94 ONLINE 0 0 0 scsi-350000393b82b6a2c ONLINE 0 0 0 errors: No known data errors I restored my CA Backup of my docker appdata folder, and it seem to have kept all my permissions in place: root@NAS01:~# ls -ln /zfs/docker total 4267660 drwxrwxrwx 8 0 0 19 Jul 27 16:14 Community_Applications_USB_Backup/ drwxrwxrwx 3 0 0 3 Jul 27 16:14 appdata/ drwxrwxrwx 3 0 0 7 Sep 12 00:11 1/ drwxr-xr-x 3 0 0 4 Aug 9 13:59 2/ drwxrwxrwx 3 0 0 3 Aug 8 14:51 3/ drwxrwxrwx 3 0 0 4 Jul 27 16:14 4/ -rw-rw-rw- 1 99 100 53687091200 Sep 12 11:23 docker.img drwxr-xr-x 4 911 911 4 Jul 27 16:14 5/ drwxrwxrwx 6 911 911 6 Jul 27 16:14 6/ drwxrwxrwx 7 1000 1000 18 Sep 11 10:10 7/ drwxr-xr-x 6 0 0 15 Jul 27 16:14 8/ drwxr-xr-x 2 1000 100 3 Jul 27 16:14 9/ drwxrwxrwx 3 1000 100 6 Sep 12 03:07 10/ drwx------ 6 1000 100 10 Jul 27 16:38 11/ drwxrwxrwx 4 0 0 4 Jul 27 16:38 12/ drwxrwxrwx 7 1000 100 15 Sep 12 02:19 13/ drwxr-xr-x 2 911 911 4 Jul 27 16:38 14/ drwxrwxr-x 7 1000 100 15 Sep 12 02:36 15/ drwxr-xr-x 2 1000 100 2 Jul 27 16:39 16/ drwxrwxrwx 8 1000 100 13 Sep 12 03:07 17/ drwx------ 4 0 0 6 Jul 27 16:39 18/ drwxr-xr-x 5 1000 100 10 Jul 27 16:39 19/ drwxrwxrwx 5 1000 100 5 Jul 27 16:39 20/ drwx------ 7 911 911 7 Jul 27 16:40 21/ root@NAS01:~# ls -ln /mnt/user/docker total 8357876 drwxrwxrwx 1 0 0 328 Jul 27 16:14 Community_Applications_USB_Backup/ drwxrwxrwx 1 0 0 20 Jul 27 16:14 appdata/ drwxrwxrwx 1 0 0 147 Sep 12 11:11 1/ drwxr-xr-x 1 0 0 47 Aug 9 13:59 2/ drwxrwxrwx 1 0 0 38 Aug 8 14:51 3/ drwxrwxrwx 1 0 0 37 Jul 27 16:14 4/ -rw-rw-rw- 1 99 100 53687091200 Sep 12 10:50 docker.img drwxr-xr-x 1 911 911 34 Jul 27 16:14 5/ drwxrwxrwx 1 911 911 57 Jul 27 16:14 6/ drwxrwxrwx 1 1000 1000 4096 Sep 11 10:10 7/ drwxr-xr-x 1 0 0 212 Jul 27 16:14 8/ drwxr-xr-x 1 1000 100 25 Jul 27 16:14 9/ drwxrwxrwx 1 1000 100 53 Sep 12 11:23 10/ drwx------ 1 1000 100 191 Jul 27 16:38 11/ drwxrwxrwx 1 0 0 40 Jul 27 16:38 12/ drwxrwxrwx 1 1000 100 238 Sep 12 11:11 13/ drwxr-xr-x 1 911 911 44 Jul 27 16:38 14/ drwxrwxr-x 1 1000 100 232 Sep 12 11:12 15/ drwxr-xr-x 1 1000 100 6 Jul 27 16:39 16/ drwxrwxrwx 1 1000 100 208 Sep 12 11:11 17/ drwx------ 1 0 0 66 Jul 27 16:39 18/ drwxr-xr-x 1 1000 100 184 Jul 27 16:39 19/ drwxrwxrwx 1 1000 100 41 Jul 27 16:39 20/ drwx------ 1 911 911 71 Jul 27 16:40 21/ (obfuscated the folder names) Yet when I move my docker volumes from /mnt/user/docker/xyz to /zfs/docker/xyz, the containers have all sorts of permissions issues writing to their config folders. For example, Plex won't start, UNMS throws permissions errors on its config folder, etc. I can't find any differences in UID/GIDs between the two docker folders, but every container I've tried so far has the same issue. Any thoughts on what I'm missing?

I'm also getting the " Timeout: No Response from localhost" error. Plugin stopped working a few days ago, and now I can't re-install it. I was able to removepkg the dependencies in case it was an issue with net-snmp or something, but a fresh install fails (see below). DNS resolution is just fine (ping localhost works without issue). plugin: installing: https://raw.githubusercontent.com/coppit/unraid-snmp/master/snmp.plg plugin: downloading https://raw.githubusercontent.com/coppit/unraid-snmp/master/snmp.plg plugin: downloading: https://raw.githubusercontent.com/coppit/unraid-snmp/master/snmp.plg ... done +============================================================================== | Installing new package /boot/packages/libnl-1.1.4-x86_64-1.txz +============================================================================== Verifying package libnl-1.1.4-x86_64-1.txz. Installing package libnl-1.1.4-x86_64-1.txz: PACKAGE DESCRIPTION: # libnl (netlink socket library) # # libnl is a library for applications dealing with netlink sockets. # The library provides an interface for raw netlink messaging and # various netlink family specific interfaces. # # Homepage: http://people.suug.ch/~tgr/libnl/ # # Executing install script for libnl-1.1.4-x86_64-1.txz. Package libnl-1.1.4-x86_64-1.txz installed. +============================================================================== | Installing new package /boot/packages/net-snmp-5.7.3-x86_64-4.txz +============================================================================== Verifying package net-snmp-5.7.3-x86_64-4.txz. Installing package net-snmp-5.7.3-x86_64-4.txz: PACKAGE DESCRIPTION: # net-snmp (Simple Network Management Protocol tools) # # Various tools relating to the Simple Network Management Protocol: # # An extensible agent # An SNMP library # Tools to request or set information from SNMP agents # Tools to generate and handle SNMP traps # A version of the UNIX 'netstat' command using SNMP # A graphical Perl/Tk/SNMP based mib browser # Executing install script for net-snmp-5.7.3-x86_64-4.txz. Package net-snmp-5.7.3-x86_64-4.txz installed. +============================================================================== | Updating /etc/rc.d/rc.snmpd to use our config file, and to reduce logging +============================================================================== Shutting down snmpd: .............................. DONE Starting snmpd: /usr/sbin/snmpd -LF w /var/log/snmpd.log -LF w /var/log/snmpd.log -LF w /var/log/snmpd.log -LF w /var/log/snmpd.log -LF w /var/log/snmpd.log -LF w /var/log/snmpd.log -LF w /var/log/snmpd.log -LF w /var/log/snmpd.log -LF w /var/log/snmpd.log -A -p /var/run/snmpd -a -c /usr/local/emhttp/plugins/snmp/snmpd.conf +============================================================================== | Testing SNMP by listing mounts +============================================================================== Couldn't find /boot mount point in SNMP output. Output: Timeout: No Response from localhost plugin: run failed: /bin/bash retval: 1

Is that this container? https://github.com/tynor88/docker-rclone That could certainly work for me, as I'm really only looking to back up a single folder via rclone to Backblaze. Will throw that container up and see what I can do thanks!

Ahhhh yes, helps if I read my own outputs Thanks! For anyone else who hits this, these options were hidden under "advanced" variables when using the UnRAID xml template. That's why I missed them.

Hey there @thomast_88, great work on the containers! I have a quick question - when I go to write to my newly mounted rclone folder, I am getting the "read-only file system" error as well when attempting to write to the folder. I used your template to deploy: Docker run command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="rclone-mount" --net="bridge" -e TZ="America/Chicago" -e HOST_OS="unRAID" -e "RCLONE_REMOTE_MOUNT"="backblaze" -e "RCLONE_MOUNT_OPTIONS"="--read-only" -e "RCLONE_CONFIG_PASS"="" -v "/mnt/user/docker/appdata/rclone":"/config":rw --cap-add SYS_ADMIN --device /dev/fuse --security-opt apparmor:unconfine -v /mnt/disks/backblaze/:/data:shared tynor88/rclone-mount:dev Docker logs output: GID/UID ------------------------------------- User uid: 911 User gid: 911 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] done. [services.d] starting services Executing => rclone mount --config=/config/.rclone.conf --allow-other --read-only backblaze /data [services.d] done. ls -l of the /mnt/disks folder: root@NAS01:/# ls -l /mnt/disks total 0 drwxrwxrwx 3 nobody users 23 Jun 12 11:25 SATA_SSD_67F407560D2400150419 drwxr-xr-x 1 911 911 0 Jun 12 16:11 backblaze drwxrwxrwx 3 nobody users 17 Jun 9 15:20 seagate Thoughts? Thanks!

Hi team! I just posted a feature request over on Github: https://github.com/linuxserver/docker-smokeping/issues/21 but thought I'd drop it here since I didn't know this forum section existed. I'm running SmokePing on Unraid 6.3.2, and I have one minor gripe with it - TCPPing doesn't work since there is no binary installed in the docker image. I've been able to install TCPPing by bash-ing into the container and manually installing it, but that seems a bit unnecessary for a Docker container. Anyone able to comment on availability of TCPPing for SmokePing? Thanks!

+1 for unRAID as an iSCSI target. My big use case is block-level access to my shares for use with various softwares that require it - BackBlaze, for example, requires block-level access to back up to their services (most cloud backup providers require this). SAN scenarios would also be a great use case.

Hey all. First off, great plugin! It works wonders to backup my Docker implementation each night. I've got two quick questions - [*]Is there a way to add a secondary backup source/dest? I'd love to backup another unrelated share to an external server mounted via the Unassigned Devices Plugin [*]Is there a way to have the notifications be sent via the system default? Right now, I use "Agent" for all notifications to get info sent via Pushover to my devices. But for some reason, CA Backup only presents browser toast notifications. Thanks for the assistance, and keep up the wonderful work!

Great, I look forward to trying it. I was going to report that the current version wasn't working for me. I am trying to move everything off of disk 3, and it appears I have plenty of room on all the other disks to clear disk 3, but unbalance is telling me there isn't enough room. It feels like it's doing its math on the one remaining folder on disk 3, which contains 1.5 TB of movies, and no single other disk has this much room, but there is almost 2TB of free space on all the other disks, so it should all fit. I'll update and try again when I get home, but wanted to report the issue anyway, in case it is a bug the hasn't gotten fixed already. Also, thanks for changing the way it works, I think it will be far more intuitive with your changes. Posted from my phone, forgive any spelling errors. +1 here - trying to migrate about 600GB of data across ~5TB of available space on the array, and it reports that there isn't enough disk space. It's like it's not splitting the folder structure across the drives, it appears as though it's just trying to move the main folder and that's that. Thoughts on how to fix this?