Has anyone run into the situation where you have a mixed environment (NIS/NFS for UNIX access; AD/CIFS for NTFS access) and in the process of changing a UNIX UID for a user it does not properly show the change for NTFS files when viewed via NFS from a UNIX box? If you run fsecurity on the ntfs file you can see that it does imbed the UNIX UID in the NTFS file itself. For unix files, it's no problem, you just chown the file to the new UID, however there does not appear to be any solution for NTFS files. I had a case open with NetApp and they say it is "merely cosmetic" and doesn't actually impact the file access or security of the file, which is all true. However if you do an LS from a unix box and see a bogus UID for a user that no longer exists, you might think the file doesn't need to be around, which is a false assumption in this case. It is merely cosmetic, however it can be horribly misleading. Why store the UID in the first place if you can't correct it when it changes.
Anyway, any insights would be appreciated.
Thanks!
Tim Thomas Lockheed Martin