dlandon

Unassigned Devices - Managing Disk Drives Outside of The unRAID Array

Recommended Posts

dlandon    93

Unassigned Devices Plugin

 

Unassigned Devices (UD) includes a lot of functionality and has become a bit complex.  Please be aware of the following before you start using UD.

  • Hover your mouse over an any active area on the UD page and a tool tip will show you what clicking that area does.
  • UD has a destructive mode that allows deleting disk partitions and formatting disks.  If Destructive Mode is not turned on in the UD Settings, you WILL NOT be able to format a disk.  Go the the Settings page and scroll to the bottom to see the UD settings.  To format a disk:
    • Destructive mode must be enabled.
    • Disk must have all partitions removed.  Unmount disk, click on the serial number, and click on all red-X to delete partitions.
    • If the disk has been precelared and shows a grayed 'Format' button, click on the disk serial number, then click on the red-X to delete the preclear status file.
  • There are different operations in various active areas (especially the disk serial number) based on whether or not the disk drive is mounted.  If the disk is not mounted, click on the '+ icon by the serial number, click on the partition name, then you can type a new mount point name.  Press Enter for the name change to be applied.  This will now become the mount point and the share name when the disk is shared.

  • In order to share any UD device, sharing needs to be enabled in the UD Settings and the switch turned on to share the particular device.

  • Disks formatted with xfs or ext4 will be mounted with 'discard'.  This enables TRIM on SSD devices.

  • DIsks formated XFS or BTRFS will be partitioned compatible with the array disks and can be installed in the array without a re-format.

 

This plugin is a continuation of the Unassigned Devices plugin originally written by gfjardim.  I have updated the plugin for unRAID 6.1.7, fixed some issues, and added new features.

 

Unassigned Devices allows you to mount and share disk drives that are not managed as part of the array.  Some users are mounting a drive specifically for Dockers and/or VMs rather than having them on a cache or array drive.  You can also mount a UNC share on another system (SMB or NFS) and have it show in the unRAID shares when browsing the unRAID shares with Windows.  This is called SMB Mount.  The UNC path is mounted locally and shared as a \\Tower share.

 

Access to Unassigned Devices shares defaults to Public with everyone having read/write access.  User access can be enabled in the Unassigned Devices Settings.  Access can be enabled by user for read/write, read only, or no access to Unassigned Devices shares.

 

When a USB device is plugged in or mounted an event is initiated to run a user defined script.  This is usefull for backing up files from the server initiated by plugging in the USB device or copying pictures from a camera to the array.  Scripts are created unique for each device.  You can also setup one script to run whenever any device is plugged in or mounted.

 

Installing the plugin

 

You can install the plugin from the Community Applications plugin or by pasting the following link in the Install Plugin tab on unARAID plugins page.

https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg
 
Mount Points and Shares

 

There seems to ba a lot of confusion over a mount point vs. a share.  The mount point is where the device is mounted locally on unRAID.  A share makes the mount point available in Windows at '\\Tower' as a browseable folder.

 

When devices and SMB Mounts are mounted, they are mounted at /mnt/disks/.  They are not a part of the unRAID array and are not mounted at /mnt/disk/ which is for unRAID disk drives.  As an example, you have a device named 'MyDisk'.  When it is mounted, it is accessed locally at /mnt/disks/MyDisk.  If you want to use 'MyDrive' in a Docker you would refer to it by '/mnt/disks/MyDrive'.  It is not automatically shared at '\\Tower\MyDrive'.

 

To share 'MyDrive', you would turn on the 'Share' switch for the drive and 'MyDrive' would be shared at '\\Tower\MyDrive'.  The share 'MyDrive' is not accessed at /mnt/user/MyDrive' because it is not an unRAID user share.

 

Mount points and shares are two separate things.

 

Partitions and Formatting

 

If you turn on the destructive mode in the Unassigned Devices Settings, you will be able to delete partitions and format disks.  It is defaulted off as a safety measure.

 

Scripts

 

Here is an example script that will back up a Pictures share to a USB drive when plugged in.  The USB drive is unmounted once the script completes so you just plug in the drive, wait for it to be completed, and then unplug the drive.  The beeps in the script will make speaker sounds if you have a speaker to let you know when the drive is plugged in, when the backup has started, and when the backup has finished and the drive unmounted.  The nice thing about this script is that all you have to do is plugin the drive and wait for it to finish.  You will also be notified when it is done if you have turned on unRAID notifications.  Set the drive to auto mount.  Set the script to run in the background.

 

If you mount and unmount the drive from the Unassigned Devices gui, the drive will mount and unmount but the script will not run because it has detected the 'OWNER' as 'user' and will skip the backup.

#!/bin/bash
PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin
## Available variables: 
# AVAIL      : available space
# USED       : used space
# SIZE       : partition size
# SERIAL     : disk serial number
# ACTION     : if mounting, ADD; if unmounting, REMOVE
# MOUNTPOINT : where the partition is mounted
# FSTYPE     : partition filesystem
# LABEL      : partition label
# DEVICE     : partition device, e.g /dev/sda1
# OWNER      : "udev" if executed by UDEV, otherwise "user"
# PROG_NAME  : program name of this script
# LOGFILE    : log file for this script

case $ACTION in
  'ADD' )
    #
    # Beep that the device is plugged in.
    #
    beep  -l 200 -f 600 -n -l 200 -f 800
    sleep 2

    if [ -d $MOUNTPOINT ]
    then
      if [ $OWNER = "udev" ]
      then
        beep  -l 100 -f 2000 -n -l 150 -f 3000
        beep  -l 100 -f 2000 -n -l 150 -f 3000

        logger Started -t$PROG_NAME
        echo "Started: `date`" > $LOGFILE

        logger Pictures share -t$PROG_NAME
        rsync -a -v /mnt/user/Pictures $MOUNTPOINT/ 2>&1 >> $LOGFILE

        logger Syncing -t$PROG_NAME
        sync

        beep  -l 100 -f 2000 -n -l 150 -f 3000
        beep  -l 100 -f 2000 -n -l 150 -f 3000
        beep  -r 5 -l 100 -f 2000

        logger Unmounting PicturesBackup -t$PROG_NAME
        /usr/local/sbin/rc.unassigned umount $DEVICE

       echo "Completed: `date`" >> $LOGFILE
        logger Pictures Backup drive can be removed -t$PROG_NAME

        /usr/local/emhttp/webGui/scripts/notify -e "unRAID Server Notice" -s "Server Backup" -d "Pictures Backup completed" -i "normal"
    fi
    else
        logger Pictures Backup Drive Not Mounted -t$PROG_NAME
  fi
  ;;

  'REMOVE' )
    #
    # Beep that the device is unmounted.
    #
    beep  -l 200 -f 800 -n -l 200 -f 600
  ;;
esac
 
Cron Task

 

A better way of running cron scripts is the 'User Scripts' plugin.  You can set up a script to run at a particular time to perform disk operations.  It is best to leave the device mounted so the script can access the drive.

 

This is a simple way to set up a cron task to run a script to copy files to a backup.  This method is a little cumbersome, but does work well.  You will need to set up your drive to auto mount and it has to be left mounted.  You can use the default script or the following one if you want beeps when the drive is mounted and unmounted.  Set the drive to auto mount.  he drive has to stay mounted for the script to work.  Set the script to run in the background.

#!/bin/bash
PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin
## Available variables: 
# AVAIL      : available space
# USED       : used space
# SIZE       : partition size
# SERIAL     : disk serial number
# ACTION     : if mounting, ADD; if unmounting, REMOVE
# MOUNTPOINT : where the partition is mounted
# FSTYPE     : partition filesystem
# LABEL      : partition label
# DEVICE     : partition device, e.g /dev/sda1
# OWNER      : "udev" if executed by UDEV, otherwise "user"
# PROG_NAME  : program name of this script
# LOGFILE    : log file for this script

case $ACTION in
  'ADD' )
    #
    # Beep that the device is plugged in.
    #
    beep  -l 200 -f 600 -n -l 200 -f 800
  ;;

  'REMOVE' )
    #
    # Beep that the device is unmounted.
    #
    beep  -l 200 -f 800 -n -l 200 -f 600
  ;;
esac
Now set up a cron file in the /flash/config/plugins/dynamix/ directory.  Name the file 'custom.cron' (or a name of your own choosing.cron) with the following contents.  This will set up a cron task to run at 4:30 AM every day.  It runs a script in the /boot/custom/ directory called DailyBackup.
# Custom cron scripts:
30 4 * * * /boot/custom/DailyBackup &> /dev/null

Sample Daily Backup script
#!/bin/bash
#
# Perform daily backup.
#

MOUNTPOINT=/mnt/disks/DailyBackup
PROG_NAME=DailyBackup

logger Started -t$PROG_NAME

if [ -d $MOUNTPOINT ]
then
  logger Pictures share -t$PROG_NAME
  rsync -a -v /mnt/user/Pictures $MOUNTPOINT/ 2>&1

  logger Completed -t$PROG_NAME
  /usr/local/emhttp/webGui/scripts/notify -e "unRAID Server Notice" -s "Server Backup" -d "Daily Backup completed" -i "normal"

else
  logger Daily Backup Drive Not Mounted -t$PROG_NAME
fi
 
After you have copied your cron file to the dynamix directory you will have to load the cron file manually one time to get it started.  unRAID will manage the cron file after that and insert it into the crontab for you.

 

Use the following command to load the cron file the first time.

/usr/local/sbin/update_cron
 
Click on the 'Help' button on the main menu bar of unRAID to get some additional help.  If you hover your mouse over an active area on the gui, you will see tool tips that will help you understand the operation of the active area.

 

There is an icon to download a zipped copy of the log for troubleshooting.

 

Verify you have the latest version installed and check the Unassigned Devices log file for information if you are having any issues.  Many questions can be answered by reading this post and checking the Unassigned Devices log.

Edited by dlandon
  • Upvote 4

Share this post


Link to post
Share on other sites
dlandon    93

Unassigned Devices Best Practices

 

Here are some best practices I recommend when using unassigned devices.

  • Be sure each device you use with Unassigned Devices has a unique label.  The mount point is the device label if there is one, but it can be changed.  Don't use the 'UNRAID' label on any devices.  That label is reserved for the boot flash drive.
  • Rename the device mount point from the default.  Unmount the disk, click on the '+' icon by the serial number, and change the mount point name to something that makes sense to you.
  • Turn on the run in the background switch for all scripts.  This will keep the webgui from hanging if a script starts while you are on the web page.
  • Don't share devices and SMB/NFS Shares unless necessary and enable SMB Security for user access when you do.
  • Leave destructive mode off until you need it.  It is too easy to delete a partition by accident.
  • Try to use a file format other than ntfs when writing to disks.  Ntfs write speed on Linux is not that good and I have had some serious problems (corruption) when writing to a ntfs disk that is full.  I use xfs on my backup USB drives.
  • While this might be quite obvious, you should not uninstall the unassigned devices plugin if you are using a drive for Dockers or VMs.  Uninstalling will unmount all mounted drives.  If the disk is busy, the unmount will be forced and you will lose access to the disk.  Updating the plugin with drives mounted is not an issue at all because they are not unmounted.
  • A drive that is not mounted will show spun down and will not show temperature unless a script file is created.  The Disk Attributes will also be disabled for the drive.  The easiest way to handle this is to click on the edit script icon, select the default script, and then save it.  The default script does not do anything with the drive.
  • There is a log file available that will log any errors from running your script file.  It is located at /tmp/ and is by the serial number or label of your drive/SMB Mount point.
  • You can test your disk script in a window.  Click on the Identification (serial number) when the disk is mounted and you'll see a lightning bolt.  Click on the lightning bolt and a window will open and run your drive script.  You'll then see any errors in your script and can make changes to fix the errors.
  • If you want to pass a device to a VM, be sure that unassigned devices does not auto mount it.  You can then pass it to a VM.  Unassigned devices will show it as connected and unmounted after you pass it through to the VM.
  • Any device mounted with unassigned devices will be included in cached directories in the Dynamix Cache Directories plugin unless specifically excluded or not included.
Edited by dlandon
  • Upvote 1

Share this post


Link to post
Share on other sites
Kir    0

What do you use NMAP for?

 

I don't understand what you are asking.

 

/boot/config/plugins/unassigned.devices/packages/nmap-6.40-x86_64-1.txz

 

I don't understand the need for nmap for this package, sorry. Could you explain what it's used for?

Share this post


Link to post
Share on other sites
dlandon    93

What do you use NMAP for?

 

I don't understand what you are asking.

 

/boot/config/plugins/unassigned.devices/packages/nmap-6.40-x86_64-1.txz

 

I don't understand the need for nmap for this package, sorry. Could you explain what it's used for?

 

I don't understand either.  I can't imagine why it is there.  I took over the work that gfjardim started and didn't pay any attention to what packages were installed because I have been concerned with getting the plugin working.

 

I will look into that, but I am thinking it has no business being there.

Share this post


Link to post
Share on other sites
dlandon    93

Thanks for the scripts. The first one is pretty much my use case.

 

I've been doing that since the SNAP days.  Really cool just to plug in a disk, have it backup on its own and notify me when it is done.  Saves time and keeps me from making mistakes.

Share this post


Link to post
Share on other sites
dAigo    0

First, I want to thank you for taking over or at least stepping in while gfjardim is inactive, much appeciated.

 

Second, I would like to renew my feature request for adding NVMe support to this plugin.

origial request & additional info

 

He said he will look into it, maybe thats the reason he is absend, still looking maybe  ;)

 

As I wrote, I suppose there would be some recoding/testing involved to resolve the missing /dev/disk/by-id issue, as it is used quite often in the code from what I can tell.

Lime-Tech startet to look into support for nvme as cache devices, but even if/when that comes, you would not mix nvme with normal sata ssd in a cache-pool, so nvme outside of the array will still be a valid option I think.

 

From what I can tell so far, apart from the naming issue that prevents it from beeing identified by the plugin every other tool/command (format/mount) should work as it does for a sata/ahci device.

 

If you need more info about nvme, I explained the manual process of identifying an individual nvme device (at least in my case) HERE

 

I would of course be willing to try inofficial releases and provide output/logs where needed.

 

Share this post


Link to post
Share on other sites
ken-ji    34

What do you use NMAP for?

 

I don't understand what you are asking.

 

/boot/config/plugins/unassigned.devices/packages/nmap-6.40-x86_64-1.txz

 

I don't understand the need for nmap for this package, sorry. Could you explain what it's used for?

 

I don't understand either.  I can't imagine why it is there.  I took over the work that gfjardim started and didn't pay any attention to what packages were installed because I have been concerned with getting the plugin working.

 

I will look into that, but I am thinking it has no business being there.

 

This I somewhat remember from gfjardim's release notes

it for detecting NFS or SMB servers I think.

Share this post


Link to post
Share on other sites

Can this coexist with gfjardim "Unassigned Devices" or is it one or the other kind of thing? I use gfjardim's version so very seldom but want to have the most up-to-date. :P

Share this post


Link to post
Share on other sites
trurl    136

Can this coexist with gfjardim "Unassigned Devices" or is it one or the other kind of thing? I use gfjardim's version so very seldom but want to have the most up-to-date. :P

See first post in thread.

This plugin is a continuation of the Unassigned Devices plugin originally written by gfjardim.  I have updated the plugin for unRAID 6.1.7 and fixed some issues ... Be sure you install the dlandon version of 'Unassigned Devices (updated)' from Community Applications.  The gfjardim version of Unassigned Devices is not working on unRAID 6.1.7...

Share this post


Link to post
Share on other sites
dlandon    93

What do you use NMAP for?

 

I don't understand what you are asking.

 

/boot/config/plugins/unassigned.devices/packages/nmap-6.40-x86_64-1.txz

 

I don't understand the need for nmap for this package, sorry. Could you explain what it's used for?

 

I don't understand either.  I can't imagine why it is there.  I took over the work that gfjardim started and didn't pay any attention to what packages were installed because I have been concerned with getting the plugin working.

 

I will look into that, but I am thinking it has no business being there.

 

This I somewhat remember from gfjardim's release notes

it for detecting NFS or SMB servers I think.

 

Correct.  It is supposed to find SMB hosts.  It is not working, is overkill, and I have read some information on the net that there may be security issues with nmap.

 

I am removing the package.  The only downside is that you have to type in the host name or IP address.  Not a big deal and because it only found the host name you were on (i.e. Tower was the only host name found), it wasn't working anyway. and not worth the time to troubleshoot.

Share this post


Link to post
Share on other sites
dlandon    93

First, I want to thank you for taking over or at least stepping in while gfjardim is inactive, much appeciated.

 

Second, I would like to renew my feature request for adding NVMe support to this plugin.

origial request & additional info

 

He said he will look into it, maybe thats the reason he is absend, still looking maybe  ;)

 

As I wrote, I suppose there would be some recoding/testing involved to resolve the missing /dev/disk/by-id issue, as it is used quite often in the code from what I can tell.

Lime-Tech startet to look into support for nvme as cache devices, but even if/when that comes, you would not mix nvme with normal sata ssd in a cache-pool, so nvme outside of the array will still be a valid option I think.

 

From what I can tell so far, apart from the naming issue that prevents it from beeing identified by the plugin every other tool/command (format/mount) should work as it does for a sata/ahci device.

 

If you need more info about nvme, I explained the manual process of identifying an individual nvme device (at least in my case) HERE

 

I would of course be willing to try inofficial releases and provide output/logs where needed.

 

I don't have the time or resources to invest in bleeding edge.  Once LT sorts it out, I can probably pick it up from there.

Share this post


Link to post
Share on other sites
John_M    14

What do you use NMAP for?

 

I don't understand what you are asking.

 

/boot/config/plugins/unassigned.devices/packages/nmap-6.40-x86_64-1.txz

 

I don't understand the need for nmap for this package, sorry. Could you explain what it's used for?

 

I don't understand either.  I can't imagine why it is there.  I took over the work that gfjardim started and didn't pay any attention to what packages were installed because I have been concerned with getting the plugin working.

 

I will look into that, but I am thinking it has no business being there.

 

This I somewhat remember from gfjardim's release notes

it for detecting NFS or SMB servers I think.

 

Correct.  It is supposed to find SMB hosts.  It is not working, is overkill, and I have read some information on the net that there may be security issues with nmap.

 

I am removing the package.  The only downside is that you have to type in the host name or IP address.  Not a big deal and because it only found the host name you were on (i.e. Tower was the only host name found), it wasn't working anyway. and not worth the time to troubleshoot.

 

It works nicely for me, finding all the SMB servers on my network. But if it's a security risk, it's no biggie to lose it.

Add_SMB_Share.png.e054ae04e025dcf7f963dde9f40b342e.png

Share this post


Link to post
Share on other sites
dlandon    93

I couldn't get it to work right on either of my servers.  That's why I gave up.  It is really no big deal to type in the host name.

Share this post


Link to post
Share on other sites
kizer    23

I just tried it and it worked... Lol

However its not that hard to simply Map a IP.

Share this post


Link to post
Share on other sites
page3    0

Thank you for fixing this and for the examples in the first post. Much appreciated.  :)

Share this post


Link to post
Share on other sites
ermethic    0

One of the very few issues I have with Unraid is that disk quotas are not implemented.

I have a Hikvision ip camera that is unable to initialize and record to a share if it is bigger than a certain size, making it impossible to use the Unraid array for this purpose.

Also I would like to setup limited shares for several users that should have access to the storage.

 

As there are quite a few obvious advantages for implementing disk quotas on shares, I would like to ask if it would be complicated to extend the functionality of this plugin by creating, mounting and sharing from an IMG file, instead of an actual disk. Each IMG would be limited from settings and shared to a different user, thus making it possible to constrain the user to a limited disk usage.

 

Apparently it is possible to create such a share from command line, as discussed in this thread, but I don't know if it would be survived on a reboot, and also making it part of this plugin would make it much cleaner and integrated in the Unraid interface.

 

Thank you very much in advance...

Share this post


Link to post
Share on other sites
jonp    68

One of the very few issues I have with Unraid is that disk quotas are not implemented.

I have a Hikvision ip camera that is unable to initialize and record to a share if it is bigger than a certain size, making it impossible to use the Unraid array for this purpose.

Also I would like to setup limited shares for several users that should have access to the storage.

 

As there are quite a few obvious advantages for implementing disk quotas on shares, I would like to ask if it would be complicated to extend the functionality of this plugin by creating, mounting and sharing from an IMG file, instead of an actual disk. Each IMG would be limited from settings and shared to a different user, thus making it possible to constrain the user to a limited disk usage.

 

Apparently it is possible to create such a share from command line, as discussed in this thread, but I don't know if it would be survived on a reboot, and also making it part of this plugin would make it much cleaner and integrated in the Unraid interface.

 

Thank you very much in advance...

This should be posted in the feature request forum.

Share this post


Link to post
Share on other sites
ermethic    0

This should be posted in the feature request forum.

 

I was thinking it's a feature request for this particular plugin, since it's probably gonna take a lot less to implement than an Unraid feature.

 

Share this post


Link to post
Share on other sites
ken-ji    34

Make a feature requesting for this setting for any share

max disk size (G)

    This option allows you to put an upper limit on the apparent size of disks. If you set this option to 100 then all shares will appear to be not larger than 100 MB in size.

    Note that this option does not limit the amount of data you can put on the disk. In the above case you could still store much more than 100 MB on the disk, but if a client ever asks for the amount of free disk space or the total disk size then the result will be bounded by the amount specified in max disk size.

    This option is primarily useful to work around bugs in some pieces of software that can't handle very large disks, particularly disks over 1GB in size.

    A max disk size of 0 means no limit.

    Default: max disk size = 0

    Example: max disk size = 1000

from https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html

 

This will let you work around your issue.

 

EDIT: made one http://lime-technology.com/forum/index.php?topic=45850.0

Share this post


Link to post
Share on other sites
ermethic    0

Make a feature requesting for this setting for any share

max disk size (G)

    This option allows you to put an upper limit on the apparent size of disks. If you set this option to 100 then all shares will appear to be not larger than 100 MB in size.

    Note that this option does not limit the amount of data you can put on the disk. In the above case you could still store much more than 100 MB on the disk, but if a client ever asks for the amount of free disk space or the total disk size then the result will be bounded by the amount specified in max disk size.

    This option is primarily useful to work around bugs in some pieces of software that can't handle very large disks, particularly disks over 1GB in size.

    A max disk size of 0 means no limit.

    Default: max disk size = 0

    Example: max disk size = 1000

from https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html

 

This will let you work around your issue.

 

EDIT: made one http://lime-technology.com/forum/index.php?topic=45850.0

 

Lovely, it's good to know there is such an option in SMB, that would probably resolve the IP camera issue.

Still, I think it would be very nice to also be able to do some kind of IMG shares, as a quick and painless implementation of quotas for external users...

Share this post


Link to post
Share on other sites
itimpi    40

Make a feature requesting for this setting for any share

max disk size (G)

    This option allows you to put an upper limit on the apparent size of disks. If you set this option to 100 then all shares will appear to be not larger than 100 MB in size.

    Note that this option does not limit the amount of data you can put on the disk. In the above case you could still store much more than 100 MB on the disk, but if a client ever asks for the amount of free disk space or the total disk size then the result will be bounded by the amount specified in max disk size.

    This option is primarily useful to work around bugs in some pieces of software that can't handle very large disks, particularly disks over 1GB in size.

    A max disk size of 0 means no limit.

    Default: max disk size = 0

    Example: max disk size = 1000

from https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html

 

This will let you work around your issue.

 

EDIT: made one http://lime-technology.com/forum/index.php?topic=45850.0

 

Lovely, it's good to know there is such an option in SMB, that would probably resolve the IP camera issue.

Still, I think it would be very nice to also be able to do some kind of IMG shares, as a quick and painless implementation of quotas for external users...

One problem I would see with the img approach would be that the full space for the maximum quota for each user would need to be allocated up front.  Something more dynamic would seem desirable unless you expect each user to use up their full quota.

Share this post


Link to post
Share on other sites
ermethic    0

Make a feature requesting for this setting for any share

max disk size (G)

    This option allows you to put an upper limit on the apparent size of disks. If you set this option to 100 then all shares will appear to be not larger than 100 MB in size.

    Note that this option does not limit the amount of data you can put on the disk. In the above case you could still store much more than 100 MB on the disk, but if a client ever asks for the amount of free disk space or the total disk size then the result will be bounded by the amount specified in max disk size.

    This option is primarily useful to work around bugs in some pieces of software that can't handle very large disks, particularly disks over 1GB in size.

    A max disk size of 0 means no limit.

    Default: max disk size = 0

    Example: max disk size = 1000

from https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html

 

This will let you work around your issue.

 

EDIT: made one http://lime-technology.com/forum/index.php?topic=45850.0

 

Lovely, it's good to know there is such an option in SMB, that would probably resolve the IP camera issue.

Still, I think it would be very nice to also be able to do some kind of IMG shares, as a quick and painless implementation of quotas for external users...

One problem I would see with the img approach would be that the full space for the maximum quota for each user would need to be allocated up front.  Something more dynamic would seem desirable unless you expect each user to use up their full quota.

 

Maybe something like this?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.