dlandon

Help me understand what it is you are expecting this feature to do. So at the moment, I mount my virtual disk images that are created by KVM into a user share (well actually to a subfolder of a user share) like so... mount -o offset=16384 /mnt/virtualisation/vm/unraid-vm/unraid-vm.img /mnt/cache/.unraid-vm/ and then I can copy files to and from it. When I'm finished then I then unmount it. umount /mnt/virtualisation/vm/unraid-vm/unraid-vm.img One problem I can forsee is that you need to get the offset, which is found by running fdisk -l on the img file and multiplying the start value by 512 Also, fdisk doesn't work on GPT disks, that requires parted.. In fact the more I look at this, not sure how feasible it is to be honest, it gets pretty complicated... That's why I asked. I am having the same concern because of the offset and trying to make it foolproof.

Help me understand what it is you are expecting this feature to do.

I'd certainly take advantage of this feature if it were implemented! I plan on doing this.

I'm not seeing this issue. Try clearing the browser cache and possibly a different browser to see if it continues.

You can set up timed purges to remove aged files based on the aged days. For example, remove aged files every hour that are older than one day. That should be sufficient for your purposes. Why do things manually?

You're a machine .... and you're doing a great job supporting this plugin! 100% Agree! I've also noticed that if you add many NFS shares in a row they will eventually stop exporting them correctly. I'll have to play around to recreate the problem. But I did find out a reboot corrects this. So for example, if you are setting up a bunch of NFS shares, adding them one by one while the array is up seems to cause them not to work properly. Easy solution is to setup all the shares you want at once, set them to auto mount and reboot. When starting the array all get mounted and exported correctly. I've not seen any issues with NFS sharing. Let me know if you continue to have problems. Provide more information if you can.

Close the dialog and open it again. It should then refresh. I am seeing this behavior and am working on it. I had tried that a couple times but apparently not enough. Took about 3/4 times for them to show up the first time. Showed up the first time every time after that. But it looks like I'm still having a problem mounting shares as I reported. I've removed the plugin and rebooted the server, no change. EDIT I actually didn't realize that they actually get mounted correctly, even in previous versions. But they still look to be mounted together and are tied together in the gui. If I mount one it actually mounts both. Both these issues will be fixed in today's release.

Close the dialog and open it again. It should then refresh. I am seeing this behavior and am working on it.

I'll work on this. I know what this is. Fixed in the next release.

Well. I'm guessing that is the reason I'm not seeing the iso file share exported. I can access the share via smb, but not via nfs, and it doesn't appear in the exports file: root@Tower:~# cat /etc/exports # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. "/mnt/user/Downloaded" -async,no_subtree_check,fsid=110 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/ISO Library" -async,no_subtree_check,fsid=120 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Karaoke" -async,no_subtree_check,fsid=111 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Movies" -async,no_subtree_check,fsid=100 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Music" -async,no_subtree_check,fsid=102 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Photos" -async,no_subtree_check,fsid=103 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/ReadyTorrents" -async,no_subtree_check,fsid=116 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Scans" -async,no_subtree_check,fsid=121 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Series" -async,no_subtree_check,fsid=106 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Torrents" -async,no_subtree_check,fsid=109 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/UMC" -async,no_subtree_check,fsid=105 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/UserHome" -async,no_subtree_check,fsid=112 172.22.1.12(sec=sys,rw) "/mnt/user/Videos" -async,no_subtree_check,fsid=104 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/appdataX" -async,no_subtree_check,fsid=117 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/cache_only" -async,no_subtree_check,fsid=114 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/dnsmasqX" -async,no_subtree_check,fsid=119 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/hide" -async,no_subtree_check,fsid=118 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/mysql" -async,no_subtree_check,fsid=108 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/tftproot" -async,no_subtree_check,fsid=115 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/xbmc" -async,no_subtree_check,fsid=107 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/docker" -async,no_subtree_check,fsid=220 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) root@Tower:~# and I do have "Enable NFS export?" set to "Yes" in the Unassigned Devices Settings. Do I need to create a script in order for the nfs share to appear? That isn't necessary for a physical drive to be shared - eg /mnt/docker I do find it confusing that I have to click the button "Add Remote SMB Share" in order to add a remote nfs share! This is a bug in SMB/NFS mounts and iso mounts. Fixed in the next release. I will also change 'SMB Shares' to 'SMB/NFS Shares' to minimize confusion.

The mount point cannot be changed from /mnt/disks/. The issue is if you try to rename the mount point from /mnt/disks/original to /mnt/disks/somethingnew, it always reverts back to /mnt/disks/original (at least in the 2016.02.29 version, I haven't updated to today's version yet) It works fine for me. Once you make the change, be sure to press enter for it to take.

I'll work on this. I know what this is.

Try turning off the 'Complete' switch at the top. It will turn off all but the physical devices table. So that's what that 'Complete' switch is for! I've always wondered. Would you consider adding a note to the help? It does do practically everything I asked for, so thank you! Added to help text in next release.

Entering an iso file that does not exist will now generate a log entry.

Try turning off the 'Complete' switch at the top. It will turn off all but the physical devices table. I've made some changes to consolidate the web page. This will be in a release today.

2. Fixed in next release. Ah, that's made it work! My ISOs are in a directory called "ISO Libraries", and I couldn't get anything to mount! One point, though - since disk shares are disabled by default, and there is some potential danger in having them enabled, could/should the default mount point be changed? Perhaps it needs to be made a configuration option? Ah, I see that it gets shared anyway, but only by SMB, (not nfs?)! You have to turn on nfs sharing in the Unassigned Devices settings. The mount point cannot be changed from /mnt/disks/.

On smaller screens like a laptop it just fits. On an iPad it is almost too wide. When it gets too wide, it folds back over itself and is quite messy.

Entering the file path and name is a bit cumbersome and I will eventually work on an alternative. If you enter a file that does not exist, it will not be added to the iso shares so that should prevent an issue trying to mount an iso that does not exist. I was just anxious to get this feature implemented to see how it works for everyone. I am running into a busy time at work and will have less time now. I rather like this feature myself as I find it useful for driver installation to a VM so the iso doesn't have to be mounted in the VM. This is a great way to update the virtio drivers in a Windows VM. Because the iso is shared in the \\Tower path, you can use it for updating other computers without having to burn a cd.

Just echoing what bonienl said to me when CA moved up to the top Yea, that's why my dog is not in this fight. Bonienl's dog is bigger than mine.

Definitely do NOT move it to the top level tabs with docker/vm/settings. To much fighting for space at that level already. First Come, First Served!!! Dang Squid, you beat me! The recycle bin plugin is not in my opinion a high enough priority to take up the limited real estate of the main menu bar, and Squid is right if I try to make shuffling the tabs around like was done for the "Apps" tab it will be a support problem I do not have time for.

OK, so this is really cool. For a while now I have been backing up my installation cd's as ISOs so I don't have to keep track of the physical media. All I had to do was add the path to the ISO file and *boom* it was shared on the network I did notice a few potential issues though: 1. Nothing is logged until you actually mount the ISO, so if you have a typo somewhere it can be hard to troubleshoot. 2. The interface lets you add an ISO file with a space in it, but when you actually try to mount the ISO, it fails. Maybe wrap the filename in quotes when passing it to the mount command? 3. New ISOs are setup to auto mount, even if you have set "Auto Mount USB Devices" to No. Seems like this should default to No all the time, or maybe the setting should be renamed to "Auto Mount Devices"? Or if you feel strongly that it is correct as-is, that is fine too. 4. After something has successfully mounted, I get this error in the log: Command not available. Cannot execute script Is it trying to load a custom script that hasn't been created? 1. What is it you feel needs to be logged? 2. Fixed in next release. 3. The "Auto Mount USB Devices" is correct and applies to plugin USB devices, not SMB or iso mounts. The auto mount operation is working as desired. 4. The script is the one you define for the iso mount just like for a physical device. The log entry is telling you that there was no script found to run. It's informational and not an error. I've changed the log entry to be more helpful

Oooo nice feature, thank you. Quick question, can you write to it or is it read only? Read only.

New release with iso file mount.

It appears that Windows adds a signature to a drive it formats and Linux does not create that same signature. Windows knows that a disk has been formatted by another OS. If you want to use a ntfs disk in Windows and unraid, you will have to partition and format it in Windows. It can then be mounted by UD and Windows.

The code to generate the nfs shares list is truncating the share name at the first space in the name. I've fixed it in the next release.