Bug 4405 - 'net idmap restore' fails to set highest uid/gidNumber, causing duplicates
Summary: 'net idmap restore' fails to set highest uid/gidNumber, causing duplicates
Status: NEW
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: winbind (show other bugs)
Version: 3.0.24
Hardware: Other Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-21 09:07 UTC by Erik Forsberg (dead mail address)
Modified: 2007-02-22 04:38 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Forsberg (dead mail address) 2007-02-21 09:07:32 UTC 
When restoring a idmap dump taken from a .tdb after reconfiguring winbind to use LDAP as backend, using 'net idmap restore', the following warning messages are shown:

ignoring invalid line [USER HWM 10002]
ignoring invalid line [GROUP HWM 10008]
USER HWM: 10000  GROUP HWM: 10000

This might not look like a problem, but unfortunately, the uidNumber and gidNumber values written to the object with object class sambaUnixIdPool are not correct - they are set to the values set in smb.conf, not to the highest values that exist in the database after the 'net idmap restore'.

As winbind, at least not in my experiments, verify that uidNumbers and gidNumbers assigned to new SIDs already exist, but instead blindly accepts the values from the sambaUnixIdPool object, the above behaviour causes duplicate uidNumber/gidNumbers after a restore from .tdb to LDAP.
Comment 1 Erik Forsberg (dead mail address) 2007-02-22 04:38:09 UTC 
Problem still in 3.0.24 compiled from sources downloaded from samba.org. 

See also: http://comments.gmane.org/gmane.network.samba.general/87502