Thanks. I think what I have up for review balances noise vs. useful information. It turns out the SMB clients ask rather often "how much space can I use", and that call normally checks your quota. That code path can stay silent when your user SID can't be mapped (in which case no quota applies).
On Sat, Feb 11, 2023 at 2:52 PM Bill Sommerfeld <sommerf...@hamachi.org> wrote: > > On 2/11/23 06:48, Gordon Ross wrote: > > Can any of you with this problem occurring please tell me what you > > found in the filesystem that triggers it? > > I believe I can trigger (and stop) the errors more-or-less at will now. > I have a home fileserver with macos clients using smb. > > For me the errors correlate with accesses to SMB shares backed by a ZFS > filesystem containing files for which the file's uid and/or gid is > unnamed (so you see a number in ls -l instead of a user or group name). > > I put my situation in the bug but I'll expand a little here. The > filesystem in question had previously -- about a decade ago -- been > exported via NFS to other macs and there were more than a few files with > non-illumos-native uids and gids. > > I'm not sure what the precise trigger is but mounting it and using the > Finder's "get info" on the top level of the share seems to be sufficient > to cause these messages to appear in the logs. > > The "zfs userspace" and "zfs groupspace" commands look like a quick way > to screen filesystems for this problem. I put a pipeline in the bug > which works for me (but it would require some tweaking if you have files > accounted to unnamed usids and gsids instead of uids and gids). > > - Bill > ------------------------------------------ illumos: illumos-discuss Permalink: https://illumos.topicbox.com/groups/discuss/T4ef0de18d0619eef-M896ace1ce25eb895865035c6 Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
