I tried searching, but did not find anything about this. I have found lots of topics on the opposite, when files are missing from user shares, but not this.

 

Like the title says, the problem I'm having is, that files are missing from disk shares. When accessing disk shares from a windows machine via network - files are missing from disk shares. The files are not gone, they actually are on the disks, where they're supposed to be. I can see them browsing via unRAID webUI, I can see them when using Midnight Commander via putty. I can even see them in user shares - no problem.

Once again - files are OK on user shares - and missing from disk shares.

 

Basically - that is really weird.

 

The one thing that comes to mind, that maybe can help to explain this, is that these files are hard links, that I have created using SSH from a little windows app I have written myself. But from my limited knowledge, it seems there is nothing special about how I did it. hence I am baffled.

The way I do create the hard links is simply use:

// This creates folder (with all missing parents up the tree) into which the hardlinks will go 
Directory.CreateDirectory(parentFolderPath);

// Creating hardlink
var command = $"ln -f \"{source}\" \"{destination}\"";
client.RunCommand(command);

I use this lib for SSH: sshnet/SSH.NET, and then via shh I simply use linux command:

ln -f

I am pretty much newb in linux, unraid, and anything not windows. Hence, I have no ideas about: is this unraid "shares" problem, is this linux problem, or the problem is in how I create the hardlinks...

 

Help, please.

Thanks in advance.

Edited June 9, 20188 yr by shEiD
Added [SOLVED] to the title

What are the access rights from root and all steps down to the missing files?

 

Any changes compared to the access rights from root and all steps down to the alternative name for the same files?

 

Your ssh command-line login might be allowed to work with paths that your Windows machine isn't allowed to access over the Samba login.

@pwm Thank you, for pointing me to the permissions. Linux file and folder permissions still always messes me up

I think I have found the problem, but want to double check.

These are the permissions for the directory tree to the missing files and the files themselves (just an example):

root@thePit:/mnt# namei -mo "/mnt/disk27/media/torrents/hardlinks/tvshows/Whatever.Show.S03"
f: /mnt/disk27/media/torrents/hardlinks/tvshows/Whatever.Show.S03
 drwxr-xr-x root   root  /
 drwxr-xr-x root   root  mnt
 drwxrwxrwx nobody users disk27
 drwxrwxrwx nobody users media
 drwxrwxrwx nobody users torrents
 drwxrwxrwx nobody users hardlinks
 drwxrwxrwx nobody users tvshows
 drw-rw-rw- nobody users Whatever.Show.S03

root@thePit:/mnt/disk27/media/torrents/hardlinks/tvshows/Whatever.Show.S03# ls -l
total 99664896
-rw-rw-rw- 2 nobody users 4193550004 May 25 13:10 Whatever.Episode.S03E01.mkv
-rw-rw-rw- 2 nobody users 2966600875 May 25 13:10 Whatever.Episode.S03E02.mkv
-rw-rw-rw- 2 nobody users 4211656180 May 25 12:58 Whatever.Episode.S03E03.mkv

So, I guess the problem is the parent folder Whatever.Show.S03 is missing an x permission drw-rw-rw-

That is exactly the folder created by my app using the standard .NET Directory.CreateDirectory() I used it because it conveniently creates the whole directory tree, if it does not exists. I tried to find some linux command that is similarly easy to use, but couldn't, so I gave up and used what I know. TBH, I gave up quite fast, about 15 minutes in. I was in a hurry, and doing it in c# was familiar and super easy.

 

Questions:

1. So, is this missing x permission on the parent directory actually the culprit? Is that why I cannot see the files on disk shares from windows via LAN?
2. If yes, how come then, that I can see the files in user shares? This one really confusing to me, still.

As for solution, then, I will probably use mkdir -p via SSH, to create the destination directory.

2 minutes ago, shEiD said:

So, is this missing x permission on the parent directory actually the culprit?

 

Yes, the x really is important since it controls if you may enter the directory.

 

Maybe Limes have forgotten to consider the x flag when they perform the file accesses in your name.

@pwm Thanks for answers.

 

I ran Tools > DockerSafeNewPerms and everything is good.