From: herbert koelman on
Hello,

Mount fails on Fedora C3 with this message: mount to NFS server 'addr'
failed: server is down.

When trying on a RedHat version mount performs well. So the NFS server
is OK.

On the fedora box I've run through all the basic checking with success
(rpcinfo, ...).

This problem appeared since I last updated system packages with up2date.

Has anyone this same problem ?
From: Tim on
On Sat, 02 Apr 2005 10:35:26 +0200,
herbert koelman <herbert.koelman(a)urbix.fr> posted:

> Mount fails on Fedora C3 with this message: mount to NFS server 'addr'
> failed: server is down.
>
> When trying on a RedHat version mount performs well. So the NFS server
> is OK.
>
> On the fedora box I've run through all the basic checking with success
> (rpcinfo, ...).
>
> This problem appeared since I last updated system packages with up2date.
>
> Has anyone this same problem ?

Yes! :-( I tried reverting back to prior versions of what I can see has
been updated, and it hasn't helped. I've tried disabling selinux and the
firewall, and that hasn't helped. I also tried reinstalling the nfs-utils
package, and that hasn't helped. I haven't yet ploughed through to find
what actually provides the functions used to *mount* using NFS.

--
If you insist on e-mailing me, use the reply-to address (it's real but
temporary). But please reply to the group, like you're supposed to.

This message was sent without a virus, please delete some files yourself.
From: Tim on
On Sat, 02 Apr 2005 10:35:26 +0200, herbert koelman wrote:

> Mount fails on Fedora C3 with this message: mount to NFS server 'addr'
> failed: server is down.

I brought this up on another news group around the same time as you did,
independently. The cause of the problem has now been identified, and
here's two fixes you can try (below). Thus far I've only tried what I
outline. I haven't yet, tried what the other guy said.


thotpoizn wrote:

>> OK, think I found it. It would appear that a big fat hairy BUG has
>> been released into production without proper testing...
>>
>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150775
>>
>> In any case, a usable workaround is to use "-o udp" in your mount
>> statement - or just add udp into your options list in /etc/fstab,
>> depending on how you are mounting.


Tim wrote:

> I just got mine working, but in a different way (although looking
> through your reference, there's an overlap).
>
> I managed to find what actually was the most recent update that botched
> things: util-linux.i386 2.12a-21 (1-Apr). I reverted back to the
> original installation (util-linux-2.12a-16) and all is well again.
>
> As to which is the best solution, I don't know... I thought NFS would
> use either UDP, by default. The nfs man page would appear to indicate
> so. I hadn't specifically configured otherwise. And I seem to recall
> that there's some good reason to prefer one over the other, but I don't
> recall the details (I see it mentioned that many servers only support
> UDP). I might guess, if specifically setting it to use UDP fixes
> things, that my other server *only* supports UDP, and the recent update
> defaults to using TCP, now?
>
> And in case my *method* of reverting to an older package was a terrible
> way to do it, I'll say what I've done so that someone may comment on
> that, too. I issued the following two command lines:
>
> rpm -ivh --force util-linux-2.12a-16.i386.rpm
> rpm -e util-linux-2.12a-21
>
> The machine I'm messing with is behind a firewall, and only prone to my
> own operational accidents. Nobody else can get their wicked way with
> it, if there's been any remote exploit security concerns with the old
> package.

--
If you insist on e-mailing me, use the reply-to address (it's real but
temporary). But please reply to the group, like you're supposed to.

This message was sent without a virus, please delete some files yourself.


--
If you insist on e-mailing me, use the reply-to address (it's real but
temporary). But please reply to the group, like you're supposed to.

This message was sent without a virus, please delete some files yourself.

 | 
Pages: 1
Next: How to uninstall openoffice rpm's?