[[6.12.1] & [6.12.2] mc shows no progressbar]

Question 

will this get fixed some time soon?

Some time passed and even now with the newer versions I can't see the progress bar in a terminalwindow with mc

[[6.12.1] & [6.12.2] mc shows no progressbar]

On 7/24/2023 at 4:34 AM, DataCollector said:

I changed both my unraid machines to unraid 6.12.3.

The problem does still exist. 🥺

Even in 6.12.4 it looks like the problem still is not solved.

[[6.12.1] & [6.12.2] mc shows no progressbar]

I changed both my unraid machines to unraid 6.12.3.

The problem does still exist. 🥺

[6.12.0.Rc2 and ZFS Z1 (Raid5) Cache - can't delete empty Folders]

So, I could test it (using mover to remove empty folder from zfs pool/cache) again yesterday.

 

In this test mover did move the empty AEV folder (after manual staring mover, it was ready in a flash [no surprise, because there was only the empty folder to move], then the AEV folder was gone from the zfs pool/cache).
I am puzzled, because before I started this Diskussion, I did do the same.

 

So now I know that I can at least use this method to remove the empty folgers from the zfs Pool/cache.

 

I thank bonienl very much for update the File Manager plugin to be possible to use it for this purpose!

 

I still think, it would be usefull and userfriendly, if the supplied tool (mc) could also work with it.

[6.12.0.Rc2 and ZFS Z1 (Raid5) Cache - can't delete empty Folders]

2 minutes ago, JorgeB said:

I cannot replicate that and there are no other reports, please enable mover logging, run the mover and post the diagnostics.

Since AEV ist now (since this Morning [geman timezone]) in use, I can not now test it again.

I will test it again in several hours

 

[6.12.0.Rc2 and ZFS Z1 (Raid5) Cache - can't delete empty Folders]

3 hours ago, JorgeB said:

Also note that if you use the mover to move the data from the pool to the array the mover will delete those empty datasets in the end.

That I tried: no. an empty (AEV) folder still exists.

 

But thanks anyway. It seems zfs may be more stable than BTRFS, but sadly it does not behave the same when making normal file operations.

😔

[6.12.0.Rc2 and ZFS Z1 (Raid5) Cache - can't delete empty Folders]

13 hours ago, bonienl said:

When the share is empty, you can use the GUI to delete it.

See Shares -> sharename -> delete

Stop: I do not want to delete the complete share including the folder on the array!

unraid uses the ZFS Pool as Cache and creates additional folders/directories inside the share on the Cache SSDs.

And I want to manually delete the folders in/on the cache SSDs.

 

I guess my description was to shallow, so I add 3 additional Screenshots

Screenshot 1: View of my Shares

Screenshot 2: View of the Pool "cachesam" (Pool of 3 Samsung NVMe SSDs zfs)

Screenshot 3: folders/directories created from unraid, because of the fact that the shares AEV and DATA usees the pool "cachesam" as cache.

 

13 hours ago, bonienl said:

Ps keep in mind a share is a folder, but a special case at the same time.

Thanks, but I do not want to kill the complete share (every folder even on the Array). I want to delete the now empty folders created from unraid because this pool is used as cache. (and yes, I do try to kill the folder from the pool directly and not from the usershare (which would include the same names folders on the Array). And I prefer to use mc and not console.)

With unraid 6.11.5 stable and BTRFS Cache it worked that way.

But since BTRFS Pools (consisting of several Disks/SSDs) are not very stable, I switched to 6.12.0-rc2 with zfs because I thought it would work the same on this file-level, except it would be more stable as BTRFS Raid.

 

13 hours ago, bonienl said:

Shares are best managed via the GUI

Yes, but I do not want to kill the user shares called AEV or DATA, I want to delete only the now empty folder(s) on only the cache disk/pool/ssds.

[6.12.0.Rc2 and ZFS Z1 (Raid5) Cache - can't delete empty Folders]

12 hours ago, JorgeB said:

If the share was created using the GUI it will create a zfs dataset, make sure it's empty and you can delete with:

zfs destroy cachesam/DATA

 

Note that if you create the folder/share manually with mkdir for example it will create a regular folder that can be normally deleted.

Like I mentioned: the folders are automatically created (from unraid) as I copy data from an external windows PC to the share (with this Cache/ZFS-Pool).