[Samba] update to cifs-mount-3.2.0-24.1.122 from .121
broke mount.cifs [.123 is still broken]
David C. Rankin
drankinatty at suddenlinkmail.com
Thu Jul 10 20:43:01 GMT 2008
David C. Rankin wrote:
> David C. Rankin wrote:
>> David C. Rankin wrote:
>>> Jerry, Jeremy, et. al.
>>>
>>> Last night's upgrade from cifs-mount-3.2.0-24.1.121 to
>>> cifs-mount-3.2.0-24.1.122 on a openSuSE 10.3 x86_64 machine broke
>>> mount -t cifs. Now attempting to mount shares results in the following:
>>>
>>> 11:10 alchemy/home/david/bin] # mount.cifs -v //nirvana/david
>>> /mnt/nirvana-david -o username=david,uid=1000,password=notmypass
>>> parsing options: username=david,uid=1000,password=notmypass
>>>
>>> Mounting the DFS root for domain not implemented yet
>>> No ip address specified and hostname not found
>>>
>>> Huh?
>>>
>>> Can I get .121 back?
>>>
>>> This is purely a client issue. Nothing is showing in the server
>>> logs with log level = 10. Client only has entries in
>>> /var/log/messages showing that the mount command was entered:
>>>
>>> Jul 3 10:51:46 alchemy sudo: david : TTY=pts/1 ;
>>> PWD=/home/david/bin ; USER=root ; COMMAND=/sbin/mount.cifs -v
>>> //nirvana/david /mnt/nirvana-david -o
>>> username=david,uid=1000,password=notmypass
>>>
>>> Help. Let me know what else I can send and I'll be happy to do
>>> it. Thanks.
>>>
>>>
>>
>> Guys,
>>
>> I did a downgrade to the latest in openSuSE/update (3.0.26a) and
>> all works as it should. It's confirmed, whatever changes were made to
>> cifs-mount-3.2.0-24.1.122 broke it.
>>
>> Let me know if I can send anything else.
>>
>
> Does anyone know if this was fixed in the .123 release?
>
Yes, David,
Now that you mention it, I have the answer! I installed:
cifs-mount-3.2.0-24.1.123
samba-winbind-32bit-3.2.0-24.1.123
samba-3.2.0-24.1.123
samba-32bit-3.2.0-24.1.123
samba-client-3.2.0-24.1.123
samba-client-32bit-3.2.0-24.1.123
and cifs is still broken. Upon install all of the Linux-to-Linux cifs mounts
immediately fail and cannot be remounted until all samba/cifs packages are
downgraded to the only available openSuSE alternative of 3.0.26a--bummer.
Am I the only one affected by this??? Is there a workaround? Can I check/send
anything else to help fix this?
--
David C. Rankin, J.D., P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
More information about the samba
mailing list