# mount //raptor/unix/FEDORA /raptor Password for root@//raptor/unix/FEDORA: ******** mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
/var/log/messages says:
Mar 8 18:09:28 harrier kernel: [ 137.431753] FS-Cache: Loaded Mar 8 18:09:28 harrier kernel: [ 137.450501] Key type dns_resolver registered Mar 8 18:09:28 harrier kernel: [ 137.487793] FS-Cache: Netfs 'cifs' registered for caching Mar 8 18:09:28 harrier kernel: [ 137.487890] Key type cifs.spnego registered Mar 8 18:09:28 harrier kernel: [ 137.487899] Key type cifs.idmap registered Mar 8 18:09:28 harrier kernel: [ 138.043492] CIFS VFS: Send error in QFSUnixInfo = -95 Mar 8 18:09:28 harrier kernel: [ 138.093133] CIFS VFS: cifs_read_super: get root inode failed
Same mount, no problem in kernel-PAE-3.7.9-205.fc18.i686
On 03/09/13 07:15, Tim Evans wrote:
# mount //raptor/unix/FEDORA /raptor Password for root@//raptor/unix/FEDORA: ******** mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
/var/log/messages says:
Mar 8 18:09:28 harrier kernel: [ 137.431753] FS-Cache: Loaded Mar 8 18:09:28 harrier kernel: [ 137.450501] Key type dns_resolver registered Mar 8 18:09:28 harrier kernel: [ 137.487793] FS-Cache: Netfs 'cifs' registered for caching Mar 8 18:09:28 harrier kernel: [ 137.487890] Key type cifs.spnego registered Mar 8 18:09:28 harrier kernel: [ 137.487899] Key type cifs.idmap registered Mar 8 18:09:28 harrier kernel: [ 138.043492] CIFS VFS: Send error in QFSUnixInfo = -95 Mar 8 18:09:28 harrier kernel: [ 138.093133] CIFS VFS: cifs_read_super: get root inode failed
Same mount, no problem in kernel-PAE-3.7.9-205.fc18.i686
Try adding "sec=ntlm" to the mount options.
The error seen with recent kernels is usually "mount error(22): Invalid argument" and adding the sec option fixes it....so this may not be related.
Bug 905929 -- nobody is interested in fixing it.
On Sat, 2013-03-09 at 08:08 +0800, Ed Greshko wrote:
On 03/09/13 07:15, Tim Evans wrote:
# mount //raptor/unix/FEDORA /raptor Password for root@//raptor/unix/FEDORA: ******** mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
/var/log/messages says:
Mar 8 18:09:28 harrier kernel: [ 137.431753] FS-Cache: Loaded Mar 8 18:09:28 harrier kernel: [ 137.450501] Key type dns_resolver registered Mar 8 18:09:28 harrier kernel: [ 137.487793] FS-Cache: Netfs 'cifs' registered for caching Mar 8 18:09:28 harrier kernel: [ 137.487890] Key type cifs.spnego registered Mar 8 18:09:28 harrier kernel: [ 137.487899] Key type cifs.idmap registered Mar 8 18:09:28 harrier kernel: [ 138.043492] CIFS VFS: Send error in QFSUnixInfo = -95 Mar 8 18:09:28 harrier kernel: [ 138.093133] CIFS VFS: cifs_read_super: get root inode failed
Same mount, no problem in kernel-PAE-3.7.9-205.fc18.i686
Try adding "sec=ntlm" to the mount options.
The error seen with recent kernels is usually "mount error(22): Invalid argument" and adding the sec option fixes it....so this may not be related.
-- From now on, at least during winter time, Im going to blame all spelling an grammar erros on the cat sitting on my chest every time I sit down at the computer....
On 03/09/13 08:32, Terry Polzin wrote:
Bug 905929 -- nobody is interested in fixing it.
This was also discussed recently on the "test" list.
I don't happen to use windows shares all that often and the ones that I have don't show the breakage that you and others are seeing. So, I don't have any opinion.
In the test list it was mentioned that....
"Apparently, NTLM has been found to be insecure so upstream doesn't want to allow NTLM connections by default any more. There may be something you can do at the server end to use NTLMv2 instead; that would probably be safer than forcing the use of NTLM."
I must say that, at the very least, it sure would be nice to have a more meaningful error message. :-)
On 03/08/2013 07:08 PM, Ed Greshko wrote:
On 03/09/13 07:15, Tim Evans wrote:
# mount //raptor/unix/FEDORA /raptor Password for root@//raptor/unix/FEDORA: ******** mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
/var/log/messages says:
Mar 8 18:09:28 harrier kernel: [ 137.431753] FS-Cache: Loaded Mar 8 18:09:28 harrier kernel: [ 137.450501] Key type dns_resolver registered Mar 8 18:09:28 harrier kernel: [ 137.487793] FS-Cache: Netfs 'cifs' registered for caching Mar 8 18:09:28 harrier kernel: [ 137.487890] Key type cifs.spnego registered Mar 8 18:09:28 harrier kernel: [ 137.487899] Key type cifs.idmap registered Mar 8 18:09:28 harrier kernel: [ 138.043492] CIFS VFS: Send error in QFSUnixInfo = -95 Mar 8 18:09:28 harrier kernel: [ 138.093133] CIFS VFS: cifs_read_super: get root inode failed
Same mount, no problem in kernel-PAE-3.7.9-205.fc18.i686
Try adding "sec=ntlm" to the mount options.
The error seen with recent kernels is usually "mount error(22): Invalid argument" and adding the sec option fixes it....so this may not be related.
Yeah! This works:
# mount.cifs //raptor/unix/FEDORA /raptor -o sec=ntlm
Should have mentioned in my first post: the server is a NetGear ReadyNAS (linux-based) storage appliance, not a PC. There is, however, no command-line access to the server's OS; just a web browser interface, with almost no authentication options.
Not to take this too OT, but I've used cifs mounts here because NFS performance sucks with the same NAS--about 300k/second on backups using dump.
On Sat, 9 Mar 2013 08:59:28 -0500 Tim Evans tkevans@tkevans.com wrote:
On 03/08/2013 07:08 PM, Ed Greshko wrote:
On 03/09/13 07:15, Tim Evans wrote:
# mount //raptor/unix/FEDORA /raptor Password for root@//raptor/unix/FEDORA: ******** mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
/var/log/messages says:
Mar 8 18:09:28 harrier kernel: [ 137.431753] FS-Cache: Loaded Mar 8 18:09:28 harrier kernel: [ 137.450501] Key type dns_resolver registered Mar 8 18:09:28 harrier kernel: [ 137.487793] FS-Cache: Netfs 'cifs' registered for caching Mar 8 18:09:28 harrier kernel: [ 137.487890] Key type cifs.spnego registered Mar 8 18:09:28 harrier kernel: [ 137.487899] Key type cifs.idmap registered Mar 8 18:09:28 harrier kernel: [ 138.043492] CIFS VFS: Send error in QFSUnixInfo = -95 Mar 8 18:09:28 harrier kernel: [ 138.093133] CIFS VFS: cifs_read_super: get root inode failed
Same mount, no problem in kernel-PAE-3.7.9-205.fc18.i686
Try adding "sec=ntlm" to the mount options.
The error seen with recent kernels is usually "mount error(22): Invalid argument" and adding the sec option fixes it....so this may not be related.
Yeah! This works:
# mount.cifs //raptor/unix/FEDORA /raptor -o sec=ntlm
Btw, for me, sec=ntlmssp and sec=ntlmv2 continue to work under all F18 kernels stably released so far.
Ranjan
Should have mentioned in my first post: the server is a NetGear ReadyNAS (linux-based) storage appliance, not a PC. There is, however, no command-line access to the server's OS; just a web browser interface, with almost no authentication options.
Not to take this too OT, but I've used cifs mounts here because NFS performance sucks with the same NAS--about 300k/second on backups using dump. -- Tim Evans | 5 Chestnut Court Linux/UNIX Consulting | Owings Mills, MD 21117 http://www.tkevans.com/ | 443-394-3864 tkevans@tkevans.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
-
Ed Greshko -
Ranjan Maitra -
Terry Polzin -
Tim Evans