From: "Gabriele Bulfon via illumos-developer" <developer@lists.illumos.org>
To: illumos-developer <developer@lists.illumos.org>
Subject: [developer] possible bug in smbfs ?
Date: Wed, 2 Oct 2024 15:29:55 +0200 (CEST) [thread overview]
Message-ID: <71393112.1414.1727875795175@www> (raw)
In-Reply-To:
[-- Attachment #1.1: Type: text/plain, Size: 1299 bytes --]
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
Music: http://www.gabrielebulfon.com
eXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanets
------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/T2325b50b338eaba9-Mb2d66cea38e7a0bb05857ed3
Delivery options: https://illumos.topicbox.com/groups/developer/subscription
[-- Attachment #1.2: Type: text/html, Size: 3301 bytes --]
next reply other threads:[~2024-10-02 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 13:29 Gabriele Bulfon via illumos-developer [this message]
2024-10-02 14:54 ` Jason King
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=71393112.1414.1727875795175@www \
--to=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).