On 06/11/10 09:12, Andrew Hotlab wrote: > > On 06/10/10 04:52, Andrew Hotlab wrote: >> Every two-three months, all users are unable to access shared folders >> because the idmap GID range became full!! >> >> What I noticed is that each time a user mounts a shared folder, his/her GID >> is incremented, and when it reaches the upper limit, the file >> log.winbindd-idmap became full of these errors: >> "nsswitch/idmap_tdb.c:idmap_tdb_allocate_id(470) Fatal Error: GID range >> full!! (max: 20000)" >> >> Can anyone kindly suggest me what is causing this behavior, or at least put >> me in the right direction? Can I activate some debug to obtain more info >> about this? >> >> Any help will be greatly appreciated: I convinced the customer to use >> Mac/BSD/Samba instead of going to Windows because I was confident it would >> have been a valid alternative, and it's hard to justify these errors… thank >> you all in advance!! >> >> Andrew > > >> idmap uid = 15000-20000 >> idmap gid = 15000-20000 > > Can you just increase the range? The setting I am using is: > > idmap uid = 500-100000000 > idmap gid = 500-100000000 > > > > Thank you Brian. > Yes, I can do it, but this will only shift the problem. I'd like to > understand the the cause of this behavior and, if applicable, find the > solution! :) > > Andrew >
I think the cause of the problem is your range is to small. Maybe it is different with the security type you are using, I am using ADS. -- Brian Gregorcy IT Manager University of Utah Department of Chemical Engineering 801.585.7170 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
