Bug 8435 - NMBD altering case of file names causes other subsystems to fail.
NMBD altering case of file names causes other subsystems to fail.
Status: NEW
Product: Samba 3.5
Classification: Unclassified
Component: Nmbd
All All
: P5 normal
: ---
Assigned To: Jeremy Allison
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2011-09-05 02:05 UTC by Linda Walsh
Modified: 2011-09-05 02:05 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Linda Walsh 2011-09-05 02:05:12 UTC
I think it is NMBD /wins that is doing this.

But after I switched to using WINS host resolution before the local 
/etc/samba/lmhosts (which has the correct host names), host and domain names
started being up-cased.

This caused multiple probs including loss of home dirs (under /home/Domain/...
which wasn't findable under /home/DOMAIN...., solved via symlink)...

But it also causes a problem in vfs_shadow_copy2, which takes the 'base
file system name', (/home', ), the snapdir, (/home/snapdir), and checks the
path to see if it exists inside one of the @GMT-date-time dirs.

Trouble is the 'symlink' for the up-cased version doesn't exist in most
snapshots (it might exist in 1?)  -- as it was only created once -- thus it wouldn't be on any diff volume -- so unless vfs_shadow_copy2 is smart enough to know that any Domain/User names in the path for that share need to have their
case ignored when it comes to pathname matching, as samba currently alter's the case of such params, then it won't work (nor any other module that looks up pathnames that have %D/%U...etc, in them)...

Rather than try to force every place to comply with samba's case mashing, it would be better to fix the case mashing and stop altering it).

Meanwhile, my snapshots won't look up... my home dirs only work because of a symlink (which likely only works due to the 'widelinks patch' I have in my code -- but not sure as they are in the path part that's in smb.conf rather than a user specified part).   

Either way, another case of Domain-Casename MASHING, causing problems.

Though filed against 3.5.11, this bug will also be in 3.6...