https://bugzilla.novell.com/show_bug.cgi?id=446388 Summary: zypper package installation is delayed by nfs stat failure Product: openSUSE 11.1 Version: Factory Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mrmazda@ij.net QAContact: qa@suse.de Found By: --- Created an attachment (id=253226) --> (https://bugzilla.novell.com/attachment.cgi?id=253226) /var/log/zypp/history I'm filing here because factory mailing list anecdotes like this seem to get ignored. On none of my systems is any system software installed on anything but local filesystems. That means even though there may be active nfs mounts, there's no reason whatsoever I can think of for upgrade processes to stat them. Usually these systems have 4 exports from my local file server mounted, including during smart or zypper updating, which I normally do in runlevel 3. Today on one of my systems zypper dup was running along normally until I reached bug 446344 , after which the delay didn't cease even though the kernels were done installing. After about four hours elapsed to install the next relatively few packages I noticed that the downloading was proceeding normally, but the installations were all hanging. Eventually I got tired of waiting, expecting mirror updates to obsolete zypper's ref data before the end of the enormous time required to do the last 100 or so packages, so I did Ctrl-C. When zypper noticed, I got a cannot stat error on an NFS mount. My only guess what happened is that it has to do with zypper replacing portmap with rpcbind. After the zypper abort I did umount -t nfs -a, then redid zypper dup, and zypper proceeded to behave normally, quickly finishing the last 99 packages. Then I tried to mount the nfs shares again, and got bug 431722 errors instead of success, after which I did rcrpcbind, tried nfs mounting again, and succeeded. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.