Everything posted by JRubenol
-
User for Usershare doesn't appear to have full write privs
Hi All, I have a user set up just for the purposes of a smb share. The user works great within my media clients and I can delete files fine (again within my media client) but when I mount the directory in my Linux client I don't seem to have write privileges. I can see things fine but I can't actually copy/paste things into the directories. My mount is straight forward: sudo mount -t cifs //192.168.0.245/Media /mnt/Tower -o credentials=/home/[myUser]/.smbcredentials Once I do that, I see my shared folders fine on my client but again, cannot copy/paste at all. In unraid settings, the user has full read/write privileges as far as I can tell. Help appreciated.
-
SAMBA DELAYS - CPU OR SOMETHING ELSE?
Thanks all for advice and helping me diagnose. I've decided to divide up my movies by first letter and to continue using unRAID with user shares. I'll keep in mind other options. unRAID docs should probably reflect this in some way to save others the unknown that I hit. All the Best
-
SAMBA DELAYS - CPU OR SOMETHING ELSE?
This is all extremely useful so I'll start by saying thank you. A bit more for my issue though. With the user share I think SHFS is maxing out my CPU to an extent that I'm actually seeing my folder time out loading. So my options are either leave unRAID and head to a standard RAID5 (not ideal but might test it.....), use disk shares, or I could in theory move my movies into sub-directories based on first letter of the movie. But I do think my answer is generally answered now, SHFS overhead appears to be maxing out CPU which is causing various issues including delayed start of up to 40 seconds and time outs of my folder. I appreciate everyone's time!
-
SAMBA DELAYS - CPU OR SOMETHING ELSE?
So I guess my question is if RAID5 would be less CPU intensive ? As I mentioned above, my buddy was running a RAID5 on this system and didn't have any issues. Just trying to learn something. Also, SHFS isn't needed for disk share?
-
SAMBA DELAYS - CPU OR SOMETHING ELSE?
Any guesses as to why the huge difference? 2-3 seconds to start a media item vs 35-45. Is it something about how unRAID handles arrays ? I'm debating if I start from scratch this weekend with Manjaro and just good old RAID5......
-
SAMBA DELAYS - CPU OR SOMETHING ELSE?
Initial tests seem to show that this resolves the problem. Trying to figure out how to create a pool and access it that way. I'm happy to continue testing and providing logs if it'll help diagnose the issue with the user share.
-
SAMBA DELAYS - CPU OR SOMETHING ELSE?
Hm I'm just not convinced that this has anything to do with the symptoms I'm seeing. Additional test: moved all media beginning in letter A to a directory (about 200 gigs) and played same file. About 5-6 seconds to start. What is a abundantly clear is that directory size (unclear if it's # of files or size of directory) is impacting the time it takes for media to start but has no impact on the media itself once it has started. To summarize: File being only file in directory plays within 2-3 seconds File being in directory with approximately 200 gigs of other files takes about 5-6 seconds File being in directory with approximately 1.8 TB of other files takes about 35-40 seconds.
-
SAMBA DELAYS - CPU OR SOMETHING ELSE?
Ok more information is needed.....very weird stuff going on. Could the amount of stuff in the directory make a difference? I just did a test of a tv show with a lot less inside and it started within 2 seconds...... EDIT: I did a test and moved the exact same file into a test directory without any other content, starts within 2-3 seconds......so my above point seems on point but I'm not sure why that would make a difference. Thoughts appreciated.
-
SAMBA DELAYS - CPU OR SOMETHING ELSE?
Agreed the CPU is ancient but given that he had great success using this for a basic server for his media, I'm thinking it's sufficient. But, what am I looking to change here? Attached screenshot of settings. https://imgur.com/a/orvujcd
-
SAMBA DELAYS - CPU OR SOMETHING ELSE?
Hi All - I inherited an older (circa 2014) server and the idea was to replace my low end Synology (418j) system with it to at minimum be my media host (with various Kodi clients in the home). Talking to my buddy who used the server before donating it to me, he did not experience similar issues serving media (probably larger sized media) so I have to think it's unRAID as he wasn't using unRAID. Trying to iron out issues before purchasing. Thanks! Setup: Kodi client on Nvidia Shield connecting to Tower (and to Synology) via smb shares. Problem: Starting media from Tower is tediously slow compared to Synology drive. Testing using same client and same movie I'm seeing start time of approximately 3-4 seconds from Synology share vs. 35+ seconds from Tower. Maybe worth noting: (1) I keep seeing a single process eating up my Tower CPU. The process is SHFS. I've found a couple older threads saying the same thing but everyone points to stopping dockers, I don't have any dockers running. Literally just a raid setup and a single user with a samba share established and "working". Currently absolutely nothing being actively served (no client playing anything) but I'm seeing SHFS using 61.6%. (2) Once media starts, it seems pretty seamless (from both Tower and Synology hosts). Log attached. tower-diagnostics-20230705-1547.zip
-
[SOLVED] New to unRAID - Shared Drives Now Failing + CPU Spikes
Closing as resolved. It ended up being a specific file tripping up Samba - still trying to figure out which one but I've narrowed it down with a file starting with the letter S so getting there. Another thread about to be started about significant performance issues but I think it's distinct from this one. Thanks all.
-
[SOLVED] New to unRAID - Shared Drives Now Failing + CPU Spikes
No luck. New log here: https://drive.google.com/file/d/1OpCeLMDBOgFuDco9wLyQ_XC2WQc49SzR/view?usp=sharing New information after messing around a bit: (1) Samba doesn't appear to be crashing as I always have access to highest level; (2) I have full rights on highest level with my user which is what I want (3) When I enter "TV_Shows" directory, things appear to work fine, divided into sub directories for DVR'd shows, I can go into these individual shows fine (4) MOVIES directory times out (about 1.8 TB inside) Then I did a bit more testing: (5) I created a new directory MOVIES2 and moved everything from MOVIES into MOVIES2 Result: Can get into MOVIES directory fine (empty directory no time out) but MOVIES2 times out (6) I moved a single movie from MOVIES2 back into MOVIES Result: I can access MOVIES fine with the single item inside, MOVIES2 continues to time out CPU still is showing huge spikes with SHFS being a resource hog (over 100%). tower-diagnostics-20230704-0727.zip
-
[SOLVED] New to unRAID - Shared Drives Now Failing + CPU Spikes
Diagnostic Logs: https://drive.google.com/file/d/1kcvoEr0x5H25FeUHCnnAzShTElxbnAiF/view?usp=sharing I'm currently on a trial run of unRAID looking to purchase. Things were going extremely well until yesterday when things starting going sideways. In particular samba shares that were working fine on multiple clients are now timing out consistently. Looking at CPU usage on unRAID web GUI I'm seeing huge spikes when I'm trying to access these shares. I can see highest level (i.e., "Media") but when I click into one of the sub-folders I'm getting a time out. Only thing that has changed is that I've moved about 3 TB of data off my Synology server over to my unRAID server. Thoughts appreciated. Although the Server is running old hardware, I think it should have no problem hosting a few samba shares . . .