After a couple of other quick tests it looks like it's not just name resolution that is the problem - I can't use the IPv6 address in /etc/fstab either.
If I use //<ipv6_address>/data as the server & share, I get this:
# mount -v /mnt/fs01data/
parsing options: rw,credentials=/home/jim/.smb
mount error: could not find target server. TCP name <ipv6_address>/data not found
No ip address specified and hostname not found
I get the same error trying to use <hostname>/data.
If I add options inet6 to /etc/resolv.conf the error doesn't change when using the ipv6 address as the servername.
Bizarrely though, if I change back to using the hostname it thinks it has resolved it to another ipv4 address:
# mount -v /mnt/fs01data/
parsing options: rw,credentials=/home/jim/.smb
mount.cifs kernel mount options unc=//<hostname>\data,ip=32.1.4.112,user=user,pass=pass,ver=1,rw,credentials=/home/jim/.smb
I'm not sure where it is getting this IP from, as it isn't anything to do with me:
OrgName: AT&T Global Network Services
OrgID: ATGS
Address: 3200 Lake Emma Road
City: Lake Mary
StateProv: FL
PostalCode: 32746
Country: US
My kernel version: 2.6.27-9-server
I am able to resolve the IPv6 address for the server using dig, ping it successfully, etc.
So it looks as though patching might still be required? I have found another link with the same patch that has some more information:
http://www.nabble.com/-PATCH--mount....d20424645.html
"The current name resolution scheme in mount.cifs is IPv4 only. Expand
it to be protocol-independent. Also take advantage of the fact that
getaddrinfo() returns a list of addresses and have mount.cifs try each
in turn until it hits one that's reachable and allows the socket to
connect."
