[opensuse] CIFS and missing files in directory listing
I have mounted a Windows 10 share on openSUSE 42.3. On the Linux side, all existing files are not shown. They exist on the Windows server, but they are not seen on the Linux side. They are accessible. But they do not show up in a directory listing. There is a description of what I think is going on here: https://www.spinics.net/lists/linux-cifs/msg14405.html I realize that 42.3 is long in the tooth. But I have no choice but to use it in the system of interest. Anyone know if this has been fixed in openSUSE? And if so, when and where? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
So, no one else sees this on openSUSE42.3? Only me? On Mon, Dec 17, 2018 at 2:52 PM Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
I have mounted a Windows 10 share on openSUSE 42.3. On the Linux side, all existing files are not shown. They exist on the Windows server, but they are not seen on the Linux side. They are accessible. But they do not show up in a directory listing. There is a description of what I think is going on here:
https://www.spinics.net/lists/linux-cifs/msg14405.html
I realize that 42.3 is long in the tooth. But I have no choice but to use it in the system of interest. Anyone know if this has been fixed in openSUSE? And if so, when and where?
-- Roger Oberholtzer
-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer composed on 2019-01-16 07:57 (UTC+0100):
On Mon, Dec 17, 2018 at 2:52 PM Roger Oberholtzer wrote:
I have mounted a Windows 10 share on openSUSE 42.3. On the Linux side, all existing files are not shown. They exist on the Windows server, but they are not seen on the Linux side. They are accessible. But they do not show up in a directory listing. There is a description of what I think is going on here:
I realize that 42.3 is long in the tooth. But I have no choice but to use it in the system of interest. Anyone know if this has been fixed in openSUSE? And if so, when and where?
So, no one else sees this on openSUSE42.3? Only me?
It's been happening to me for years, but between OS/2 LANMAN and Linux. Random whole directories look empty to ls and mc, but in fact are not to an app that wants to open one. Function is normal from the OS/2 side, so I just work from it (usually), or use smbclient (rarely). I brought this up on a samba mailing list long ago, bug never got enough traction to even file a bug, and similar in OS/2 fora. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Jan 16, 2019 at 8:21 AM Felix Miata <mrmazda@earthlink.net> wrote:
Roger Oberholtzer composed on 2019-01-16 07:57 (UTC+0100):
On Mon, Dec 17, 2018 at 2:52 PM Roger Oberholtzer wrote:
I have mounted a Windows 10 share on openSUSE 42.3. On the Linux side, all existing files are not shown. They exist on the Windows server, but they are not seen on the Linux side. They are accessible. But they do not show up in a directory listing. There is a description of what I think is going on here:
I realize that 42.3 is long in the tooth. But I have no choice but to use it in the system of interest. Anyone know if this has been fixed in openSUSE? And if so, when and where?
So, no one else sees this on openSUSE42.3? Only me?
It's been happening to me for years, but between OS/2 LANMAN and Linux. Random whole directories look empty to ls and mc, but in fact are not to an app that wants to open one. Function is normal from the OS/2 side, so I just work from it (usually), or use smbclient (rarely). I brought this up on a samba mailing list long ago, bug never got enough traction to even file a bug, and similar in OS/2 fora.
Sigh. We have a couple transducers that have only Windows support. So we have to have a Windows computer in the configuration. We are trying to make it be as hidden as possible. It is fully controlled from the openSUSE system via Windows daemons we have written. Part of the data collection involves verification that all has been collected. And we want to do that on the Linux computer that is the one the users actually use. Missing files in directory listings is a real problem. One thing we do is ensure that a file name to collect data does not already exist. So, we need to get an accurate directory listing from the remote system. This must surely be a major problem for anyone using CIFS. I cannot believe that it is just staying that way. What is unclear to me is exactly where the problem is. In the kernel CIFS driver? In openSUSE 42.3, it is /lib/modules/4.4.114-42-default/kernel/fs/cifs/cifs.ko Is it a matter of updating this module? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/16/2019 12:57 AM, Roger Oberholtzer wrote:
So, no one else sees this on openSUSE42.3? Only me?
On Mon, Dec 17, 2018 at 2:52 PM Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
I have mounted a Windows 10 share on openSUSE 42.3. On the Linux side, all existing files are not shown. They exist on the Windows server, but they are not seen on the Linux side. They are accessible. But they do not show up in a directory listing. There is a description of what I think is going on here:
https://www.spinics.net/lists/linux-cifs/msg14405.html
I realize that 42.3 is long in the tooth. But I have no choice but to use it in the system of interest. Anyone know if this has been fixed in openSUSE? And if so, when and where?
-- Roger Oberholtzer
I'm betting you need to enable SMB1 CIFS/server on the Win10 side, see https://social.technet.microsoft.com/Forums/en-US/9fd07a6b-62dc-40b0-995c-5a... IIRC this is one issue in the Linux->Win10 access scenario. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Jan 16, 2019 at 8:53 AM David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
I'm betting you need to enable SMB1 CIFS/server on the Win10 side, see
https://social.technet.microsoft.com/Forums/en-US/9fd07a6b-62dc-40b0-995c-5a...
IIRC this is one issue in the Linux->Win10 access scenario.
It was disabled. So I wonder what was being used on the Windows side instead? I see in the Linux setup for the mount I have vers=3.02. I wonder if enabling this opens up the required ports in the Windows firewall. Given that it was not running before, I'm not sure if any problem would be that even if it is now running, maybe the firewall is doing something that effects which Windows server really is doing stuff. There is obviously something other than SMB/CIFS as the share was being served. The checkers will explore and report back if this helps. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Jan 16, 2019 at 8:53 AM David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
I'm betting you need to enable SMB1 CIFS/server on the Win10 side, see
https://social.technet.microsoft.com/Forums/en-US/9fd07a6b-62dc-40b0-995c-5a...
IIRC this is one issue in the Linux->Win10 access scenario.
This did not help. Some existing files are not shown in a directory listing. But they can be accessed by name. This is happening in the login shell. So it is not a KDE/GNOME/etc issue. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I have seen some claim that adding noserverino to the CIFS mount command helps with this problem. It has not made a difference for me. Then again, I have this in /etc/fstab: //lcms/LCMSF /media/LCMS/F cifs soft,credentials=/etc/cifs.creds.rst63,noserverino,sec=ntlm,vers=3.02,rw,noauto,x-systemd.automount,x-systemd.idle-timeout=60,nofail,_netdev,uid=rst 0 0 But mount does not show the option: //lcms/LCMSF on /media/LCMS/F type cifs (rw,relatime,vers=3.02,sec=ntlmssp,cache=strict,username=rst,domain=RST63-LCMS,uid=1000,forceuid,gid=0,noforcegid,addr=10.1.3.2,file_mode=0755,dir_mode=0755,nounix,mapposix,rsize=1048576,wsize=1048576,actimeo=1,_netdev) So can I be sure the option is active? On Thu, Jan 24, 2019 at 11:34 AM Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
On Wed, Jan 16, 2019 at 8:53 AM David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
I'm betting you need to enable SMB1 CIFS/server on the Win10 side, see
https://social.technet.microsoft.com/Forums/en-US/9fd07a6b-62dc-40b0-995c-5a...
IIRC this is one issue in the Linux->Win10 access scenario.
This did not help. Some existing files are not shown in a directory listing. But they can be accessed by name. This is happening in the login shell. So it is not a KDE/GNOME/etc issue.
-- Roger Oberholtzer
-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/24/2019 05:38 AM, Roger Oberholtzer wrote:
I have seen some claim that adding noserverino to the CIFS mount command helps with this problem. It has not made a difference for me.
Then again, I have this in /etc/fstab:
Roger, I've googled at bit and have not found a silver bullet. About the closed was: https://askubuntu.com/questions/1028100/missing-folders-in-windows-network-s... Which is a short read, but I don't think it adds anything (but does show how to check all the mount options via gvfsd-fuse). Is there anything logged? Journal, /var/log, (I'm not quite sure where it would show up). If the files are accessible by name but don't show up, that almost sounds like there make be a file ACL issue where ACLs were inadvertently set or erased so that you have read access, but browsing is disabled? I had an issue several years ago (Linux mounts), but can't quite recall the details. It may be worth poking around with 'getfacl; on the Linux side to see what the files that can be accesses show. This is more a "something to check" rather than "this is your problem" issue. A couple of links: https://linuxconfig.org/how-to-manage-acls-on-linux https://wiki.archlinux.org/index.php/Access_Control_Lists Report back if/when you find the culprit. I'm interested in what the problem is -- just can't be more help in solving it. (no Windows 10 to share) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
David C. Rankin -
Felix Miata -
Roger Oberholtzer