TexasUnraid

I could not figure out a way to disable trash but I did figure out how to change the delete shortcut so the del key will delete instead of move to the trash. settings > configure shortcuts > search "delete" change "alternate delete" shortcut from crtl+del to del. Now when you press del the files will be deleted instead of moved to trash.

I have to say, you build dockers after my own heart, you are my go to docker when it is available. Is it possible to change the default folder that krusader opens to? Or change where the home button goes? It is kind of annoying to always have to back out of the home folder before doing anything.

Thats what I thought but was trying to explain the slow performance I have seen with UD since day one. I had both SSD and spinning rust on UD. The transfer yesterday was an HDD, I know for a fact that drive should be doing ~120-150mb/s with the files I was copying based on prior copies of the same files when I was using windows. Pretty much the slowest that drive ever goes except with small files is ~100mb/s. There is some kind of bottleneck as watching the performance in netdata will show bandwidth is limited to a fixed number, generally between 40-60mb/s. CPU usage is fine and the drive is only at 10-30% utilization time (aka, it is only at 10-30% of total bandwidth). I know at one point I tested copies with krusader and saw some really strange results. When writing to an NTFS drive my READ speeds would be capped at roughly half the speed it should be but writes would be fine (they would burst at full speed thanks to the ram buffer). When writing to a BTRFS drive reading from an NTFS drive, the speeds would be fine on both ends IIRC. Only thing I could explain is some kind of NTFS driver issue.

Does UD mount the drives under the fuse file system? I have noticed that my speed with UD can be really slow, on par with using the fuse file system and I can't figure out why this is the case. Seems like it should not be using the fuse file system since it is not mounted under /user but right now I am doing a file copy and it is only going at 30-40mb/s and the drive is only at 10-15% utilization? It should be going closer to 150mb/s. Any idea where the bottleneck is? I know the hardware can handle it as I easily saw 150mb/s when using the same hardware on windows. An NTFS driver issue maybe?

I have this on one of my drives as well, pretty sure it is just a leftover partition from windows formatting. Don't worry about it. I reformatted the drive for use in the array and everything is working fine with a single partition.

Are you sure it is logging in properly? It did this to me when I tried to use the host name for the log in, when I switched to the IP address it loaded them properly. You can also try typing in the share manually and see if it works.

Try using the IP address instead of the computer name. I have an SMB windows 10 share mounted with all default settings on windows and unraid. Make sure capitalization is correct as well.

Oh, I found the cleanup script needed a similar update with quotes as well when trying to clean up the mess I made while sorting this out lol #!/bin/bash #description=This script cleans up snapshots. #arrayStarted=true #argumentDescription= -i <Comma separated list of shares to purge> or -a to purge all #argumentDefault=-i share_name_here shopt -s nullglob INCLUDE= POSITIONAL=() while [[ $# -gt 0 ]] do key="$1" case $key in -i|--include) INCLUDE="$2" shift # past argument shift # past value ;; -a|--all) ALL=YES shift ;; *) # unknown option POSITIONAL+=("$1") # save it in an array for later shift # past argument ;; esac done set -- "${POSITIONAL[@]}" # restore positional parameters #Tokenize include list declare -A includes for token in ${INCLUDE//,/ }; do includes[$token]=1 done #iterate over all disks on array for disk in /mnt/disk*[0-9]* ; do #iterate over each timestamp for timestamp in ${disk}/.snapshots/* ; do #iterate over each share in the timestamp for snap in $timestamp/* ; do if [ -n "${includes[$(basename "$snap")]}" ] || [ "$ALL" = "YES" ] ; then echo "Purging - $snap" btrfs subvolume delete "$snap" fi #check for empty timestamp if [ ! "$(ls -A $timestamp)" ] ; then echo "Purging empty directory - $timestamp" rmdir $timestamp fi done done done Thanks again for this script! Can't wait to see snapshots added to unraid GUI, either officially or in plugin form.

Been getting closer to putting my server into service and was setting up this snapshot script when I noticed it did not support folders with spaces in them. After some trial and error I got it working on folders with spaces, although the exclude option still doesn't work with spaces and I can't figure out how to get it working. The argument option of user scripts also seems to only support a single argument passed to the script and does not support spaces either. Here is the updated script with all the $share variables wrapped in quotes and timezone changed to CST: #!/bin/bash #description=This script implements incremental snapshots on btrfs array drives. #arrayStarted=true #argumentDescription= -n|--number <MAXIMUM NUMBER OF SNAPSHOTS TO RETAIL> #argumentDefault=-s 3 shopt -s nullglob #make empty directories not freak out date=$(TZ=America/Chicago date +@CST-%Y.%m.%d-%H.%M.%S) #standardized datestamp MAX_SNAPS=3 EXCLUDE= is_btrfs_subvolume() { local dir=$1 [ "$(stat -f --format="%T" "$dir")" == "btrfs" ] || return 1 inode="$(stat --format="%i" "$dir")" case "$inode" in 2|256) return 0;; *) return 1;; esac } POSITIONAL=() while [[ $# -gt 0 ]] do key="$1" case $key in -n|--number) MAX_SNAPS="$2" shift # past argument shift # past value ;; -e|--exclude) EXCLUDE="$2" shift # past argument shift # past value ;; *) POSITIONAL+=("$1") # save it in an array for later shift # past argument ;; esac done set -- "${POSITIONAL[@]}" # restore positional parameters #ADJUST MAX_SNAPS to prevent off-by-1 MAX_SNAPS=$((MAX_SNAPS+1)) #Tokenize exclude list declare -A excludes for token in ${EXCLUDE//,/ }; do excludes[$token]=1 done #iterate over all disks on array for disk in /mnt/disk*[0-9]* ; do #examine disk for btrfs-formatting (MOSTLY UNTESTED) if is_btrfs_subvolume $disk ; then #check for .snapshots directory prior to generating snapshot if [ -d "$disk" ]; then if [ ! -d "$disk/.snapshots/" ] ; then mkdir -v $disk/.snapshots fi if [ ! -d "$disk/.snapshots/$date/" ] ; then mkdir -v $disk/.snapshots/$date fi fi #iterate over shares present on disk for share in ${disk}/* ; do #test for exclusion if [ ! -n "${excludes[$(basename "$share")]}" ]; then #echo "Examining $share on $disk" is_btrfs_subvolume "$share" if [ ! "$?" -eq 0 ]; then #echo "$share is likely not a subvolume" mv -v "${share}" "${share}_TEMP" btrfs subvolume create "$share" cp -avT --reflink=always "${share}_TEMP" "$share" rm -vrf "${share}_TEMP" fi #make new snap btrfs subvolume snap -r "${share}" "/mnt/$(basename $disk)/.snapshots/${date}/$(basename "$share")" else echo "$share is on the exclusion list. Skipping..." fi done #find old snaps echo "Found $(find ${disk}/.snapshots/ -maxdepth 1 -mindepth 1 | sort -nr | tail -n +$MAX_SNAPS | wc -l) old snaps" for snap in $(find ${disk}/.snapshots/ -maxdepth 1 -mindepth 1 | sort -nr | tail -n +$MAX_SNAPS); do for share_snap in ${snap}/*; do btrfs subvolume delete "$share_snap" done rm -rfv "$snap" done fi done

Been playing around with the settings, I found that reducing the cache depth down to 5 and the cache pressure to 1 drastically reduced the CPU usage. Now it just spikes up to ~7-10% usage every few seconds instead of stilling at 20-30% for 50-60% of the time. Just need to figure out the ideal depth it seems. If I am going more then 5-6 folders deep on a drive it will most likely need to be spun up anyways I figure. Interestingly, excluding SSD shares that I know have a lot of folders in them does not seem to reduce the CPU usage much if at all.

I am guessing you are saying that it is scanning the cached version of those folders since the drives are spun down and it can't read the actual folders? How fast does linux drop the cache? Is there a way to extend it? I am not worried about memory usage since I have 32gb and only use like 8gb unless running VM's. Seems like it would be able to go more then ~10-20 seconds between scans?

Curious about this as well, My CPU normally sits around ~3-5% but with the folder cache enabled it spends almost half the time around ~20-30% usage. Not using the /user option and also mostly default settings. Seems really excessive when it should not be doing anything once the folders are cached.

Great, very handy additions!

Very cool! You sure work fast!

I wondered if that might be the case. I tried with BTRFS which seemed to say it supports labels. Also had an XFS drive in the UD I think.

Does that actually change the partition name? I did that but when I cleared the config file when troubleshooting they all reverted to the default names. This lead me to believe that the names UD displays are just share names and not actually changing the partition names?

When I mount an NTFS drive it shows me the partition name that I game it in windows. I use these to keep drives in order (personal backup 1, personal backup 2, Media backup 1, media backup 2 etc). It is really hard to keep track of the drives without these drive / partition names. Does linux not support partition/drive names like windows? There is no way to label the drives to keep track of them across systems? If I needed to use the backup drives, there is a high likely hood they would need to be used in another system.

Along these lines it would be nice to be able to change the partition name on devices. I keep data on different drives and it can be difficult to keep track of them without the partition labels. Particularly if using them on another system.

Good idea, turns out that the backup I made with dirsyncpro prior to moving the drive to the array was still active and was accessing the folder from disks and that seems to of caused the issue. Didn't think about that since it was not supposed to be doing anything. Thanks for the quick responses!

It is like there is some kind of symlink that is connected to the drive, if I stop the array, the folder disappears from /mnt/disks/ but comes back if I start the array, even with UD uninstalled.

Good idea but sadly no, I knew these drives would be moved to the array so I was careful to not link anything to the /mnt/disks path since I knew it would change. Plus none of my dockers currently interact with the drives directly, they are just shared to the network for now as that is what they were doing when on windows.

As I said above, I did that already and checked the cfg file in flash and made sure it was removed as well.

It is showing up in the array in the GUI but it is still mounting the share under /mnt/disks that the drive used to be attached to when it was being used by UD. I even uninstalled unassigned devices completely and rebooted and the drive STILL mounted in /mnt/disks/, not even sure how that is possible? This is why I am scared to use the drive in the array, it should not be being mounted to the /mnt/disks, so something is wrong.

I am finally in the process of setting up my array. I was using my NTFS drives mounted via UD for the last few weeks to get the server setup. I won't need the server today, so my plan was to move the drive to the array and start copying the data over to it as it should take around 24 hours for the copy to complete wit my old drives and thus would be back up about the time I need it. I made a backup of the drive to some other drives, I then moved it to the array from UD and formatted it. I started the array and was about to start copying data to it when I noticed that it is still mounting it under the unassigned devices share name?? I have tried putting the drive back in UD, mounting and unmounting the drive, deleting the config and then adding it back to the array. Didn't help. I deleted the symlink in disks, didn't work. I rebooted several times, didn't work. I even uninstalled unassigned devices completely and rebooted and the drive STILL mounted in /mnt/disks/, not even sure how that is possible? I don't know what else to try, I don't want to waste time copying data if I might need to reformat the drive again to fix this.

Ok, I am lost. I was experimenting with passing through drives to a VM, I then removed then from the VM, deleted the VM and am trying to share them like I used to. The issue is that all the drives that were passed through as now only being shared as read only, drives that were not passed through work fine. I have restarted the server several times I removed the configuration files for the drives by disconnecting them and clicking the X on historical devices I changed all the read only, passthrough and other settings on and off again I changed the unassinged devices share settings to all the different options, restarting samba between each one and restarting the whole server between many of them. All the settings are setup exactly the same as when everything was working fine now but drives are still mounted read only?? I have no idea what else I could try or do. Is there a way to completely reset unassigned devices and all associated settings to stock? EDIT: I just tried making a new folder with krusader and it is also read only there. So they are actually mounted as read only even though the config file on the flash drive doesn't have a read only line in it? edit2: Found a fix that seems to work: https://askubuntu.com/questions/70281/why-does-my-ntfs-partition-mount-as-read-only ntfsfix /dev/sdxX # where x is HDD and X is drive number, in my case it was /dev/sda1 Then unmount and remount the drive. Apparently if the drives are not cleanly shutdown in windows, windows leaves files on the drive that prevent it from mounting as writable in linux. The above command clears those files it seems. Another little tip I found to help unassinged devices show up in SMB faster is to run samba restart from CLI and they will instantly show up.