public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Jason King <jason.brian.king@gmail.com>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] possible bug in smbfs ?
Date: Wed, 2 Oct 2024 14:54:00 +0000	[thread overview]
Message-ID: <SJ2PR20MB7155C771225954BA610C13B0A4702@SJ2PR20MB7155.namprd20.prod.outlook.com> (raw)
In-Reply-To: <71393112.1414.1727875795175@www>

[-- Attachment #1: Type: text/plain, Size: 2599 bytes --]

There is a share option ‘abe’ (access based enumeration). If enabled on a share, clients will only see the files they have some sort of access to. You could try disabling that and see if the results are more what you expect.

I suspect the difference in behavior is probably related to when specifying an exact filename as a parameter to ls, it tries to do a stat(2) (or the SMB equivalent), while a glob will get expanded by the shell, and the needs to enumerate the contents of a directory (which is where the abe option may come into play) to figure out what the expansion is (which if it succeeds, is then passed as parameters to the command).



From: Gabriele Bulfon via illumos-developer <developer@lists.illumos.org>
Date: Wednesday, October 2, 2024 at 8:30 AM
To: illumos-developer <developer@lists.illumos.org>
Subject: [developer] possible bug in smbfs ?
Hello, we have an illumos system with many zones, and a separate illumos system sharing CIFS folders in workgroup mode.
Each zone mounts a dedicated share with just its own permissions, using smbfs.
After some time we realized something wierd was happening: in some folders running just "ls" from the zone shows only 125 files while on the storage dataset ther are more than 1000. File permissions are ok, all the same.
More, missing files are different and random from zone to zone on their dedicated smb share.
Even more, missing files can be accessed from the zone specifying a full file name, but are missing when using "*":

root@z153:/export/home/dos/ariansped# ls ftparia.log
ftparia.log
root@z153:/export/home/dos/ariansped# ls ftparia.*
ftparia.*: No such file or directory

Is there any known bugs in this cifs client implementation?

Thanks,
Gabriele


Sonicle S.r.l. : http://www.sonicle.com<https://www.sonicle.com/>
Music: http://www.gabrielebulfon.com<http://www.gabrielebulfon.com/>
eXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanets

illumos<https://illumos.topicbox.com/latest> / illumos-developer / see discussions<https://illumos.topicbox.com/groups/developer> + participants<https://illumos.topicbox.com/groups/developer/members> + delivery options<https://illumos.topicbox.com/groups/developer/subscription> Permalink<https://illumos.topicbox.com/groups/developer/T2325b50b338eaba9-Mb2d66cea38e7a0bb05857ed3>

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/T2325b50b338eaba9-Md24e7f6e984bb3b2a05c150a
Delivery options: https://illumos.topicbox.com/groups/developer/subscription

[-- Attachment #2: Type: text/html, Size: 6842 bytes --]

  reply	other threads:[~2024-10-02 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 13:29 Gabriele Bulfon via illumos-developer
2024-10-02 14:54 ` Jason King [this message]
2024-10-03  7:31   ` Gabriele Bulfon via illumos-developer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ2PR20MB7155C771225954BA610C13B0A4702@SJ2PR20MB7155.namprd20.prod.outlook.com \
    --to=jason.brian.king@gmail.com \
    --cc=developer@lists.illumos.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).