yaku

Dear all, after doing some changes in my disk configuration (replacing all drives, shrinking the array), I finally got this configuration, which apparently is working properly. Is there any reason to close the gap DISK2 (means to shift DISK3 to DISK2) and to have the Parity-Drive being Parity 1 instead Parity 2 or is it irrelevant (which I hope)?! Or would it be just an easy procedure to change? Want to prevent to rebuild parity or a disk another time. Otherwise, I would leave it like this. Thanks for your support! Best regards Marcus

I'm not sure about the reasons but, finally, it works. Switch to SMB 3.1.1 fixed the different behaviour between Windows and Linux client for me. The confusion obviously came from that the Plugin seemed to be unable to create the directory .Recycle.Bin. But, if this is definitely the reason and why this problem came up, I don't know. After I created the directory by hand everything works normal (so far), from Windows and from Linux side. Best regards, Marcus

Quiet easy. In /etc/fstab I have //XXXXX/XXXXX /media/XXXXX cifs vers=3.1.1,username=XXXXX,password=XXXXX,user,uid=1000 0 0 and Linux is doing the rest. The vers=3.1.1 statement I added this evening because I got aware, that Windows is using SMB vers 3.1.1 and Linux only 3.0.2 by default. But unfortunately nothing improves by having 3.1.1 also an Linux. If I execute smbstatus at the Unraid console, it now looks like this: Samba version 4.9.5 PID Username Group Machine Protocol Version Encryption Signing ---------------------------------------------------------------------------------------------------------------------------------------- 6468 XX users 192.168.49.67 (ipv4:192.168.49.67:55360) SMB3_11 - partial(AES-128-CMAC) 7669 XX users 192.168.49.88 (ipv4:192.168.49.88:64923) SMB3_11 - partial(AES-128-CMAC) Service pid Machine Connected at Encryption Signing --------------------------------------------------------------------------------------------- XXX 7669 192.168.49.88 Tue Apr 23 07:28:47 PM 2019 CEST - - IPC$ 6468 192.168.49.67 Tue Apr 23 07:19:13 PM 2019 CEST - - XXX 6468 192.168.49.67 Tue Apr 23 07:19:13 PM 2019 CEST - - Locked files: Pid Uid DenyMode Access R/W Oplock SharePath Name Time -------------------------------------------------------------------------------------------------- 7669 1000 DENY_NONE 0x100081 RDONLY NONE /mnt/user/multimedia_nas3 . Tue Apr 23 19:28:47 2019 7669 1000 DENY_NONE 0x100081 RDONLY NONE /mnt/user/multimedia_nas3 . Tue Apr 23 19:28:47 2019 For me, it looks pretty similar. The .88 machine (Windows) is working, the .67 (Linux) does not. And, additionally, I got aware that from Windows it's also not working properly. At the screenshot you see 2 different files which have been deleted. They are from different shares. And although they have been logged, the second share is not displayed (.Recycle.Bin has not been created, file not been moved). As the plugin obviously recognized, that a file has been deleted, shouldn't there be not also a error message in a log (because he failed to create the directory and to move the file)? Where can I find this? I'm a bit confused. Maybe I should work first that it's working properly with Windows and postpone the Linux problem . My Config: Unraid 6.7.0-rc7 Basic. 3x2TB Data, 1x2TB Parity, 2x60GB SSD Cache. ASRock Q1900-ITX, 16GB Memory. Maybe someone has an idea. Hope, this was bit of a kind understandable. If not, of course I'll try to dig deeper and come back, if there is anything more clear, or solved, or... Best regards, Marcus

No, I don't mean Unraid itself. I mean a seperate client computer running Linux and accessing Unraid share via CIFS mount. Regards, Marcus

Hi dlandon, sorry to ask back, but where is the difference? Thought, 'til now, CIFS/ SMB is quite the same. How is detected by Unraid that the requesting client is Linux, not Windows? How and why is Unraid handling this request? Is there any way, e.g. using a different way for connecting to the share, to get it work? Best regards, Marcus

I'm wondering recycle bin is working properly when I'm using Windows to access the shares but does not when using Linux. Any issues known? Do I have to make a special config (e.g. special SMB-version for that? Does not work means, there is no action at all. The .Recycle.Bin directory is not created, no files are moved. during deletion. The shares are connected as CIFS-fstype, so should be the same SAMBA-connection as from Windows, right? If there is already any described issue, shame on me that I've not found it. Then just be clement. Best regards and thanks in advance for any help, Marcus