Iker

Probably I should start putting together a FAQ on the first thread page:

The update fixed an issue with the mountpoint being displayed as "undefined" for zvols, it was reported by an user via dm; the full support for zvol is coming, but is going to take me a while.

Hi @dopeytree I think this article will help you to understand how snapshots work on ZFS (https://arstechnica.com/information-technology/2020/05/zfs-101-understanding-zfs-storage-and-performance/) and better plan your policy. You can always check how much space a snapshot is using with the "Snapshots Admin" dialog on the plugin. @couzin2000 I have seen that error multiple times with different plugins, it's not directly related to this plugin, so you should post it to General support thread.

New update with the following changelog: 2024.03.31 Change - Convert to dataset reporting on dataset row Add - Unraid notifications for Convert to Dataset Fix - Compatibility with 6.13 beta Fix - for folder listing corner cases Fix - for zvols mounting point

The convert to dataset functionality is just a convenient way of copying the data without having to execute the commands, but you can always do it manually. Create a dataset and the respective child ones, and start syncing each folder to the corresponding dataset from the source using rsync.

When you create a dataset at the root level, Unraid detects it as an user share. It's working as intended. It's very simple: When you unlock a dataset, you're also mounting it, so you can access the content in the mountpoint (/mnt/data/media). When you lock the dataset, the mountpoint still exists as a folder, so you can write anything to it because it's a normal folder within the system.

Fair enough, as I said, this is still a work in progress, and your feedback is very much welcome. @d3m3zs As the other disks are sleeping and the last refresh date doesn't change, I suggest you post the problem on the unassigned devices plugin thread.

Some questions that could help to pinpoint the issue source: Are the other pool disks sleeping? "Last refresh" date changes? Do you have other processes/plugins accessing the folders/files stored on that pool?

@MowMdown I have been thinking about reworking the entire snapshot admin dialog, but it is still in the draft phase. However, what you suggest maybe even more problematic than the current approach. Many people using ZFS have tens, if not hundreds, of snapshots in a single dataset, and displaying that inline along with the dataset will be a nightmare for you as a user and for me as the developer. Right now, I'm more inclined to directly present snapshots grouped by date (no more than ten buckets) on the contextual menu and implement another contextual menu for the dataset with all the related actions. But if you folks have any other ideas, I'm more than open to reading them.

New update with the following changelog: 2024.03.03 Fix - Dataset name validation before convertion Fix - rsync command for folders with whitespaces or special characters Fix - Errors on empty exclusion patterns Add - Compatibility with 6.13 beta

Sorry, I'm very reluctant to delete data without user verification; I prefer you folks verify that everything is fine and the data that you need is already in the dataset, and then and only then, you manually delete the source folder; this prevents accidentally losing data in case of unexpected errors. As I said before, I'm working on changing the dialog for conversion to a progress bar integrated on the main UI.

Hi @Larz the situation that you mention is something that I imagine may happen with large transfers, as the dialog is dismissed if the page refreshes or if any other notification/dialog appears; however, as the rsync process is running in the background, everything should be fine, and when finished, the plugin should give you a new dialog with the process result. I'm currently working on building a progress bar that appears at the right side of the dataset name to indicate any ongoing transfers and allow you folks to perform multiple transfers simultaneously.

Hmmm, maybe there is a bug on the plugin side when handling datasets with empty spaces because those are allowed on OpenZFS. I'll check if that's the case and issue a new update with the fix.

The error indicates that the system ran out of file handles, probably because rsync is trying to copy many files. Try increasing the "Max User Watches" using the "Tips And Tweaks" plugin to fix it.

By default all folders on the root level are shown; if you want to delete or convert those folders to dataset, you can enable destructive mode on the settings.

Little update with the following changelog: 2024.02.15 Fix - Directory Listing not Working

@Nonoss I just reproduce the bug, let me check a little bit deeper and I'll release a new version with the fix. @Revan335 I'll se what I can do, but not a priority right now. @dopeytree Can you elaborate your question, I mean, the description is very accurate on the steps that the plugin follows for converting a directory to a dataset. @sasbro97 You have to delete those datasets at the root manually.

No for the backup, yes for the documentation. You can configure policies and send all the dataset descendants without too much trouble. Check Syncoid or ZnapZend; those solutions automatically take care of that part and help you stay organized.

ZFS snapshots don't work like you think; a snapshot applies exclusively to one and only one dataset (There are exceptions like clones, but that's another subject). The "recursive" option means that you will also take a snapshot for every child dataset. However, that doesn't mean that the parent dataset will include the data from the child datasets; those snapshots are associated with their respective dataset. BTW, check the send command documentation on how to send snapshots incrementally and process datasets recursively.

It's associated with an option on the settings "Dataset Icon Alert Max Days", it means that the latest dataset snapshot is older than the amount of days specified on that config flag. @frodr This is a known issue with ZFS on Unraid, not this particular plugin, here is a nice summary on how to destoy a dataset if you face that error.

Little update with the following changelog: 2024.02.10 Add - "-X" option for Connvert Dataset rsync command Fix - Directory Listing detecting datasets as folders

Sure thing: I didn't notice that is detecting the dataset as a folder because of the exclusion pattern.

From your screenshot, it doesn't look like you configure that correctly. Check this comment and how the user deal with the situation, because is exactly the same as yours.

What do you mean?, Is the plugin failing to create the dataset? Is the data incomplete in the new dataset? If it is just that the temp folder is not deleted, that's by design and is stated in the convert to Dataset dialog. If we want to avoid data loss, it's preferable to have the original data still in place and delete it by hand once you don't need it.

Yes it was a typo, thanks for the note. Yes, it can be added without too much trouble; I'll wait a little bit for more feedback, but be sure that it will make it into the next version. BTW I just notice that the -r option was kept, it's an error (-a already includes -r), please suggest other rsync options that may be beneficial for the copy process.