search for: cifsaclmount

...usion, this seems to be related to cifsacl. > It's still hard to say at this point. > > cifs.idmap logs messages in the syslog. > Can you try mounting with cifsacl, then look at logs in one window > > # journalctl --since=now > > While you do a > > # ls -l /path/to/cifsaclmount/some_file > > If a mapping fails you should see something like this: > > cifs.idmap[8370]: key description: cifs.idmap;0;0;39010000;os:S-1-5-18 > cifs.idmap[8370]: Unable to convert cifs.idmap;0;0;39010000;os:S-1-5-18 to UID: Some IDs could not be mapped. > > "os" mea...

On 9/24/20 1:06 PM, Rowland penny via samba wrote: > OK, you are using users & groups in the 1000-29999 range, why ? could > it be that you have the same users in /etc/passwd and AD ? On my Linux installs, I allow for a 'local' account with user id 1000. That is the only local account and is used for installing the OS (or in case AD is down). All other user/group accounts are

...say at this point. >>> >>> cifs.idmap logs messages in the syslog. >>> Can you try mounting with cifsacl, then look at logs in one window >>> >>> # journalctl --since=now >>> >>> While you do a >>> >>> # ls -l /path/to/cifsaclmount/some_file >>> >>> If a mapping fails you should see something like this: >>> >>> cifs.idmap[8370]: key description: cifs.idmap;0;0;39010000;os:S-1-5-18 >>> cifs.idmap[8370]: Unable to convert >>> cifs.idmap;0;0;39010000;os:S-1-5-18 to UID: Some...

...cl. >> It's still hard to say at this point. >> >> cifs.idmap logs messages in the syslog. >> Can you try mounting with cifsacl, then look at logs in one window >> >> # journalctl --since=now >> >> While you do a >> >> # ls -l /path/to/cifsaclmount/some_file >> >> If a mapping fails you should see something like this: >> >> cifs.idmap[8370]: key description: cifs.idmap;0;0;39010000;os:S-1-5-18 >> cifs.idmap[8370]: Unable to convert >> cifs.idmap;0;0;39010000;os:S-1-5-18 to UID: Some IDs could not be >&...

...orks properly and shows no > overlap/confusion, this seems to be related to cifsacl. It's still hard to say at this point. cifs.idmap logs messages in the syslog. Can you try mounting with cifsacl, then look at logs in one window # journalctl --since=now While you do a # ls -l /path/to/cifsaclmount/some_file If a mapping fails you should see something like this: cifs.idmap[8370]: key description: cifs.idmap;0;0;39010000;os:S-1-5-18 cifs.idmap[8370]: Unable to convert cifs.idmap;0;0;39010000;os:S-1-5-18 to UID: Some IDs could not be mapped. "os" means it's the file owner (Owne...

...usion, this seems to be related to cifsacl. > It's still hard to say at this point. > > cifs.idmap logs messages in the syslog. > Can you try mounting with cifsacl, then look at logs in one window > > # journalctl --since=now > > While you do a > > # ls -l /path/to/cifsaclmount/some_file > > If a mapping fails you should see something like this: > > cifs.idmap[8370]: key description: cifs.idmap;0;0;39010000;os:S-1-5-18 > cifs.idmap[8370]: Unable to convert cifs.idmap;0;0;39010000;os:S-1-5-18 to UID: Some IDs could not be mapped. > > "os" mea...