Bug 821859 - ncplogin fails to mount volume
ncplogin fails to mount volume
Product: Fedora
Classification: Fedora
Component: ncpfs (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Orphan Owner
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-05-15 11:28 EDT by Armands Liepins
Modified: 2013-07-31 20:16 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-31 20:15:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Armands Liepins 2012-05-15 11:28:03 EDT
Description of problem:
After issuing "ncplogin -S <SERVERNAME> -A <SERVERNAME> -U <username>"
it throws message:
failed:ncplogin: No such file or directory attempt to open mount point
and the whole home directory becomes empty, causing a big trouble. It can be unmounted with #umount <SERVERNAME>/<USERNAME>, returning system to normal state. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. ncplogin -S <SERVERNAME> -A <SERVERNAME> -U <username>

Actual results:
empty home directory

Expected results:
volume SYS mounted under ~/ncp/<SERVERNAME>/SYS

Additional info:
The server is netware 5 and TCP/IP connection to the server is used.
Comment 1 Alex Sm 2012-06-01 08:14:06 EDT
IMHO the same bug:
Fedora 17
kernel 3.3.7-1.fc17.i686

When trying mount netware volume get message:
ncpmount: No such device in mount(2)

There is no module ncpfs.ko in kernel/fs/ncpfs directory.

Developers, please, compile this module in next kernel version.
Comment 2 Alex Sm 2012-06-04 04:48:51 EDT
Sorry. I found ncpfs.ko in kernel-modules-extra rpm.
ncpmount works fine, except "Can't get /etc/mtab~ lock file" error.
Comment 3 Miguel Angel 2012-06-25 02:37:44 EDT
Fedora 17
kernel 3.4.3-1 (x86_64)

(same as Alex Sm) ncpmount: No such device in mount(2)

I've strace'd it and noted that the second parameter to "mount()" system call is set to "." (current directory???????) no matter what I specify in the "ncpmount" command.

It works fine under Arch Linux, and the second parameter to "mount()" is set correctly.
Comment 4 Miguel Angel 2012-06-25 10:23:39 EDT
Sorry! I believed I installed "kernel-modules-extra"... but I double-checked it and realized I did not.

Now it works fine (except the "Can't get /etc/mtab~ lock file" issue).
Comment 5 Fedora End Of Life 2013-07-03 18:23:09 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2013-07-31 20:16:04 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.