From Bugzilla Helper: User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.9-31 i686) Description of problem: We use ncpmount to rsync our Novell 4.2 server thru a rh7.2 box to a server with a tape drive: ncpmount -S NovellBox /mnt/Novell -U UUUUUUUU -P PPPPPPPP cd /mnt/Novell rsync -essh -avz --exclude=sys/ --ignore-errors . /var/novell Result: rsync starts ... building file list ... link_stat . : Stale NFS file handle then exits This function has worked for 18-months-or-so until last week when we upgraded from 2.4.9-31smp to 2.4.18-27.7xsmp. The Novell Volume mounts ok. I can cd to: /mnt/Novell/vol1 I can execute: ls -laR I can NOT execute: find /mnt/Novell -print I can NOT execute: rsync ... I can execute: cp -p some-file /tmp/ Wazzup ? Version-Release number of selected component (if applicable): ncpfs-2.2.0.18-6 kernel-smp-2.4.18-18.7.x How reproducible: Always Steps to Reproduce: 1. ncpmount -S novell-box /mnt/novell -U UUUUUUUU -P PPPPPPPP 2. cd /mnt.novell 3. rsync -essh -avz --exclude=sys/ --ignore-errors . some-target/ Actual Results: rsync starts ... building file list ... link_stat . : Stale NFS file handle Expected Results: Incremental backup of Novell files to a Linux Directory Additional info: This __did__ work with ncpfs-2.2.0.18-6 and kernel-smp-2.4.9-31 See Above
I forgot to mention I saw a similar bug via google on the LKML: http://www.uwsg.iu.edu/hypermail/linux/kernel/0209.2/1612.html Also Andrew Morton has 'fixed' ncpfs for the 2.5 tree just today: http://linuxtoday.com/news_story.php3?ltsn=2003-02-16-003-26-NW-KN-DV ... Andrew Morton <akpm>: ... o ncpfs compile fix o de4x5 compile fix Also in Steps to Reproduce, Step 2 should read: cd /mnt/novell Thanks again. -- kjh
Installed kernel-smp-2.4.18-27.7.x.i686.RPM ncpmount now works. Thanks !
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/