[[6.0-beta6] User Share Copy Bug]

The symlink idea is not something that's going to get into -beta7 and probably not in 6.0-final.  Just too many other critical features to address.

 

What we're going to do is create some warning notice on the Share Settings page that talks about this issue: that it's not recommend to copy files directly from a disk share to user share UNLESS: the source disk is not configured to be part of user shares.

 

That is, on the Share Settings page, there are "global" Include/Exclude masks.  Say for example, you want to empty all the files from "disk2" to the user share file system.  What you would do is set "Excluded disks(s)" to "disk2" and click Apply.  Now it should work fine to copy everything off disk2 to a user share, letting shfs decide where to write things.

 

There's really no other way to prevent user from shooting himself in foot without giving up some other functionality.

 

I don't want to change the meaning of the share-level Include/Exclude masks, again proper documentation is required here as well.

 

I just tried this and it did NOT work.  Maybe an array restart is required.. but this didn't work by just hitting apply. The file went into limbo as if I never excluded the disk.

It does work if you rename the source directory to something different first (and there is at least one disk that already has the share directory).

Note this was tried from the command line..  not from windows...  if that makes a difference.

 

[[6.0-beta6] User Share Copy Bug]

The symlink idea is not something that's going to get into -beta7 and probably not in 6.0-final.  Just too many other critical features to address.

 

What we're going to do is create some warning notice on the Share Settings page that talks about this issue: that it's not recommend to copy files directly from a disk share to user share UNLESS: the source disk is not configured to be part of user shares.

 

That is, on the Share Settings page, there are "global" Include/Exclude masks.  Say for example, you want to empty all the files from "disk2" to the user share file system.  What you would do is set "Excluded disks(s)" to "disk2" and click Apply.  Now it should work fine to copy everything off disk2 to a user share, letting shfs decide where to write things.

 

There's really no other way to prevent user from shooting himself in foot without giving up some other functionality.

 

I don't want to change the meaning of the share-level Include/Exclude masks, again proper documentation is required here as well.

 

I just tried this and it did NOT work.  Maybe an array restart is required.. but this didn't work by just hitting apply. The file went into limbo as if I never excluded the disk.

It does work if you rename the source directory to something different first (and there is at least one disk that already has the share directory).

Note this was tried from the command line..  not from windows...  if that makes a difference.

 

Nevermind...  I misread Tom's instructions.  I didn't use the global "don't use for shares"  I did the local exclude in the share settings.

[[6.0-beta6] User Share Copy Bug]

I just changed my settings to allow disk shares..  Let me see if I understand it...

 

Say I have a share called DVD.

Say I have a folder called MyMovie on Disk 1.

 

I want to move it to disk 2 (or some other disk) to free up disk 1.

 

So

cp /mnt/disk1/DVD/MyMovie    /mnt/disk2/DVD would work perfectly fine?

 

But if I did

 

cp /mnt/disk1/DVD/MyMovie    /mnt/user/DVD    would lose the whole MyMovie folder?

 

Now what if I exclude disk1 from the share DVD clicked apply  and then did

 

cp /mnt/disk1/DVD/MyMovie    /mnt/user/DVD

 

Would it then work fine and unraid would move the file to some other disk of it's choosing?

 

I routinly used to copy from one disk share to another disk share to free up some space and such.  I don't think I ever tried a disk to user share move/copy.

But I'd like to understand the limitation.

 

 

[6.10.3 Samsung 980 Temp Warning]

Someone asked for the steps I used.  So here they are.,

 

1. download the ISO image from the Samsung website. (Link above - make sure you grab the correct image)

2. Make a bootable USB flash drive from the ISO. (I used Rufus - but I'm sure there are others) I did this on Windows.

3. If you feel paranoid, I would make sure you have a everything on your cache drive backed up. - I didn't lose data but better to be safe than sorry.

4. Shutdown Unraid.

5. Yank Unraid flash drive and put in the Samsung ISO image drive you just created.

6. boot the Samsung image and follow the prompts to update the firmware. Some folks had issues with a USB keyboard  in the past.  I had no issues.

7. Power down the unraid machine again

8. take out the Samsung flash drive and put back in the Unraid flash drive.

9. Power on the Unraid machine and verify you have the updated firmware.

[6.10.3 Samsung 980 Temp Warning]

I was able to update using the ISO image on the samsung website

I got it from here.  It scared the hell out of me as it warned  ~"This will or may erase all data"

So I just did one at a time (I have two) and each were fine.  No data was erased!

Some folks on other website claimed that the ISO didn't work and described how to do it manually.

I didn't have to go that route, thankfully...

[6.10.3 Samsung 980 Temp Warning]

I was having this issue too.  Further along the article linked above talks about updating the firmware of the drive to fix this as well.  To me that seems like a better fix...  But I'm not sure how I would go about updating the FW! It seems a little scary! 🙂