d3m3zs

@Iker would like to ask you - is it possible to show refresh date in system date format? Or at least add options in plugin settings to setup format?

These 3 files Then #ZFS snapshots cp -rf "$source_dir"znapzend/ /usr/local/bin/ chmod +x /usr/local/bin/znapzend chmod +x /usr/local/bin/znapzendzetup chmod +x /usr/local/bin/znapzendztatz #Run znapzend service znapzend --logto=/var/log/znapzend.log --daemonize # Check if znapzend is running pgrep znapzend > /dev/null if [[ $? -ne 0 ]]; then /usr/local/emhttp/webGui/scripts/notify -i warning -s "znapzend is not running" fi If plugin will be updated - fine, but don`t expect and don`t need it. Also, you can take a look at Sanoid for snapshots and replicas, it is even easier, only one config and plugin updated. Also author of both plugins is the same eprson and he (or she) mentioned that switched to Sanoid.

Download https://github.com/oetiker/znapzend/releases/download/v0.23.2/znapzend-0.23.2.tar.gz Unpack, go to folder "bin" and you will find all 3 files. Copy them to any place and use, of course according to place where you put them will be diff command to execute. Or paste them to /usr/local/bin to be able run without path, but need to write simple cp script to do this every boot. Create script to run during every Array starts: /HERE_IS_YOUR_PATH/znapzend --daemonize --pidfile=/var/run/znapzend.pid

And nothing happens: When Array starts I have the same default config: Help only manually change smb-shares.config and restart service: So, does anybody know why "Samba extra configuration:" ignored?

You don`t need any additional script. When you install Sanoid plugin, config folder will be created by path: /etc/sanoid Copy them to any not system folder, for example on cache drive and edit sanoid.conf file: [pool/dataset] use_template = production recursive = yes [template_production] hourly = 0 daily = 7 weekly = 4 monthly = 3 yearly = 0 autosnap = yes autoprune = yes That is all what you need, it is exactly config that will be automatically created by mentioned SpaceInvaders script. Now to execute snapshot (it will be automatically create snapshots and delete old according to config): sanoid --configdir=/mnt/pool/dataset/sanoid_configFolder --cron If you need extra details - add "--verbose" If you need send snapshots: syncoid -r pool1/dataset1 pool2/dataset2 No additional script needed, no extra logic implemented. You can extend this config file by adding other pools and datasets, you can add other templates or you can even create another config file. One huge minus of Sanoid - it will automatically wake up all ZFS HDD drives in system, even if they are not related to current config file. For example if I need create snapshot of one dataset on cache nvme pool every 15 minutes - all my ZFS HDD in system will be also spin up every 15 minutes, because Sanoid uses "zfs list" command under hood for every run.

concatenation doesnt work here https://github.com/oetiker/znapzend/blob/master/doc/znapzendzetup.pod https://metacpan.org/pod/strftime Plugin doesn`t add any additional functionality. For example I even don`t use this plugin, I downloaded znapzend, took 3 files and use them, after each array start I automatically run command: All your question related to znapzend itself and should be addressed to their github as support request.

Could you please update plugin to last version? Plugin uses v 0.21.2, but on github already 0.23.2. And also do you have any plan for feature developemnt?

I understand, thank you. It is almost the same what I asked, will be happy to have it.

Thanks for your reply! I checked plugin ZnapZend, it includes old version, much better to download lastest from repo. Also plugin does nothing, except add znapzend to system, no GUI and no any interface. If you add znapzend - everything will be in one place.

Yesterday tested znapzend for the first time and really liked it, even much more than Sanoid/Syncoid. Just get 3 files and use them (znapzendzetup, znapzend, znapzendztatz). I don`t know what exactly you use in your plugin, but would be great to add support znapzendzetup and znapzend (just 2 small bin files): znapzendzetup - just edit, disable, delete and create plan and no more else, maybe simple text dialog? Would be awesome to have it in Zfs master plugin. znapzend - maybe for fast execution, or maybe znapzendzetup would be enough. znapzend --recursive --autoCreation --runonce=pool/dataset Just my thoughts. Honestly, it will be best tool ever for Unrain if it supports replication with schedule, send/receive and removing old snapshots by policy, need to add znapzend itself and simple dialog for edit plan.

Did you find the reason? The same

I mentioned this thread in my first post here and then mentioned what did I achieve. Do we know how smb-extra.conf works? It will rewrite original smb-shares.conf or just add few parameters?

I expected to see something in the guide or documentation, taking into account adding support of ZFS in Unraid.

No reply? How to automate this? II would like to add vfs objects = shadow_copy2 and all other parameters to each zfs share. If I am right should be something like path = /mnt/user/downloads comment = browseable = yes writeable = no read list = write list = admin valid users = admin case sensitive = auto preserve case = yes short preserve case = yes vfs objects = shadow_copy2 catia fruit streams_xattr fruit:encoding = native shadow: snapdirseverywhere = yes shadow: snapdir = .zfs/snapshot shadow: sort = desc shadow: format = %Y-%m-%d-%H%M%S shadow: localtime = no

Works only if I add manually vfs objects = shadow_copy2 shadow: snapdirseverywhere = yes shadow: snapdir = .zfs/snapshot shadow: sort = desc shadow: format = %Y-%m-%d-%H%M%S shadow: localtime = no to share in file /etc/samba/smb-shares.conf

cat /etc/samba/smb-shares.conf returns [downloads] path = /mnt/user/downloads comment = browseable = yes writeable = no read list = write list = admin valid users = admin case sensitive = auto preserve case = yes short preserve case = yes vfs objects = catia fruit streams_xattr fruit:encoding = native I have seen this post But didn`t helped, after array starts - nothing applied. I manually changed /etc/samba/smb-shares.conf reloaded samba (/etc/rc.d/rc.samba restart) And I see nothing here

Thank you, already setup btrbk tool with few scripts, 2 configs and automatically copy btrbk itself from boot drive to /usr/local/bin. Plugin is good only for visualization, unfortunately (I don`t want to offend anyone) plugin looks like limited and unfinished: no manual, no error explanation, no validation for user mistake, very primitive and illogical user experience. From my experience it the most outdated and messy plugin from all list of installed plugins. Yes, but for example unraid still has no monitoring for BTRFS errors, found workaround: And after all these nuances instead of improving current functionality Lime Technology, Inc. decided to add ZFS improvemnts, it reminds me Xiaomi smarthones when they release new model each week and forget about support old one.

But this one comes from plugin, not my fault. Thank you, so plugin is totally not ready and has no simple validation and even human-readable log. Now I understand why BTRFS so unpopular - because even Lime Technology, Inc. is not interested in simple UI for maintaining BTRFS file system. I added "@" for snapshot just to better distinguish on destination after sending. Trying to figure out what is the best flow for snapshots, really don`t see many information, only one positive thing from plugin - is visibility of available snapshots, but even here some mess.

Also setup job and got snapshots: btrfs snapshot send -p / /mnt/cache/.snapshots/docker_2025-Jan-Sat_00:30:10 To /mnt/disk4/btrfs_snapshots/ Error ERROR: empty stream is not considered valid Would be great to have any explanation, don`t understand what is wrong with settings. Have no idea what is "empty stream" Run one more time and got snapshots: btrfs snapshot send -p /mnt/cache/.snapshots/docker_2025-Jan-Sat_00:30:10 /mnt/cache/.snapshots/docker_2025-Jan-Sat_00:31:57 To /mnt/disk4/btrfs_snapshots/ Error ERROR: snapshot: cannot find parent subvolume d09791c2-0608-f342-b4ae-e3d736714ad6 At snapshot docker_2025-Jan-Sat_00:31:57 But if I press "Send" - snapshot will be sent to disk4. Also doesn`t clear why on disk4 received snapshots don`t separated from subvolume Snapshots - 2023.07.16 Unraid - 7.0.0-rc.2

Oh thank you, weird, but didn`t notice. And one more question - what is maybe best way to store snapshots - each inside particular subvolume or maybe create one "snapshots" subvolume for all disk and store them there? I mean example: 1. /mnt/cache/.snapshots/docker_{Y-M-D_H:i:s} 2. /mnt/cache/docker/.snapshots/docker_{Y-M-D_H:i:s}

I suppose since Current Version2023.07.16 no updates and no plan to improve? For example system folder has a lot of snapshots and no options to collapse them, just huge list.

Thank you! Safe mode helped. I discovered that the problem was related to one or more of my installed plugins. By rebooting into normal mode and removing plugins based on their last update date, I resolved the issue. In attachment picture I highlighted plugins that I removed. Although I haven't pinpointed the exact culprit, I suspect 'System Statistics' might be involved. I don`t want to debug it now, because parity sync is running.

Ok, but what can affect it? I already stopped a few services - didn`t help. Docker is already stopped. And removed a few plugins - also didn`t help.

XFS - no issues, ZFS has issues. For me it is pretty clear and I understand that "it is not normal". I am asking here because I need solution, I like haave bigger pool than splitted by few separate. Also on reddit I see many posts when users switched back to XFS even for pool after all experiments, so I am not alone. Can anyone check my diagnostic logs to provide solution? I use "Open Files Plugin" there is nothing extraordinary and all can prevent shutdown.

VM and Docker are stopped. Even after reboot with turned off both services I couldn’t again stop array. Only one workaround- turn off auto start array and reboot system. If it is possible to fix, according to diagnostics log - great, but I temporarily splitted raidz1 pool to 3 separate pools formatted in XFS and have zero issues, very responsive system, very fast docker container installation and also no problems with stopping array. Absolutely the same config and services, it seems something is wrong with ZFS implementation in Unraid.