Re: Getting an odd message when trying to NFS mount the sles9root tree
> This is a temporary situation and it's an old dusty/crusty > linux installation that is getting replaced as soon as this > temporary move of the > SLES9 installation server is accomplished. Assuming your network is reasonably reliable (in terms of not dropping things too often), then it's something you can safely ignore. As others have commented, it's just telling you that it's falling back to UDP, and if you have a reliable network, that's not a problem. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Getting an odd message when trying to NFS mount ...
I see you've gotten several replies. But no one specifically addressed this part of the message you're getting: > Using NFS over UDP can cause data corruption. I think it would be more accurate to say "Using NFS over UDP with '-o soft' can cause data corruption." By default, the "hard" option is set for NFS mounts, so that even when using UDP, your risk of data corruption is greatly reduced. Hard NFS mounts have a problem on the other end of the spectrum: If the server from which you mounted that vol goes down, then your client is hung until it comes back. That is, rather than risk data corruption, you are more likely to get stuck depending on another host. THe "soft" option is a way around THIS problem, but leads to the potential for data corruption. Probably more info than you wanted. -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Getting an odd message when trying to NFS mount the sles9root tree
This is a temporary situation and it's an old dusty/crusty linux
installation that is getting replaced as soon as this temporary move of the
SLES9 installation server is accomplished.
David Boyes
<[EMAIL PROTECTED]
e.net> To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: Getting an odd message when
trying to NFS mount the sles9root
10/03/2005 10:16 tree
AM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
> I have to make a new SLES9 installation server because I'm
> upgrading the current sles8 server I use for that to sles9. I
> get this message:
>
> vadnais:~ # mount -t nfs
> gsop23nnn09:/cd_images/SLES9/sles9root /sles9root nfs server
> reported tcp not available, falling back to udp Using NFS
> over UDP can cause data corruption.
>
> Does this mean something is scrozzled on the system I'm
> mounting it on, or something is scrozzled on the server where
> the sles9root exists. I am at a loss to explain why it is
> saying TCP is unavailable since I can access both of those images.
While TCP in general may be available, NFS over TCP may not be. It's a
configuration option, and it sounds like whoever installed the NFS server
allowed it to default to NFSv2 which spoke only UDP. Check your NFS server
configuration and make sure NFSv3 is enabled.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Getting an odd message when trying to NFS mount the sles9root tree
> I have to make a new SLES9 installation server because I'm > upgrading the current sles8 server I use for that to sles9. I > get this message: > > vadnais:~ # mount -t nfs > gsop23nnn09:/cd_images/SLES9/sles9root /sles9root nfs server > reported tcp not available, falling back to udp Using NFS > over UDP can cause data corruption. > > Does this mean something is scrozzled on the system I'm > mounting it on, or something is scrozzled on the server where > the sles9root exists. I am at a loss to explain why it is > saying TCP is unavailable since I can access both of those images. While TCP in general may be available, NFS over TCP may not be. It's a configuration option, and it sounds like whoever installed the NFS server allowed it to default to NFSv2 which spoke only UDP. Check your NFS server configuration and make sure NFSv3 is enabled. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Getting an odd message when trying to NFS mount the sles9root tree
On Oct 3, 2005, at 8:45 AM, James Melin wrote: I have to make a new SLES9 installation server because I'm upgrading the current sles8 server I use for that to sles9. I get this message: vadnais:~ # mount -t nfs gsop23nnn09:/cd_images/SLES9/sles9root / sles9root nfs server reported tcp not available, falling back to udp Using NFS over UDP can cause data corruption. Does this mean something is scrozzled on the system I'm mounting it on, or something is scrozzled on the server where the sles9root exists. I am at a loss to explain why it is saying TCP is unavailable since I can access both of those images. Probably the server is using a fairly old NFS server using only NFSv2, or very conservative compatibility settings, or some such. NFS-over-UDP was the only kind of NFS for a long long time. Check the settings for the NFS server on gsop23nnn09, and see what they are. The warning is probably harmless: lots of people used NFS over UDP just fine for many years, and only occasionally did th NFS server dogbreath not responding; still retrying... -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Getting an odd message when trying to NFS mount the sles9root tree
> -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of James Melin > Sent: Monday, October 03, 2005 8:45 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Getting an odd message when trying to NFS mount the > sles9root tree > > > I have to make a new SLES9 installation server because I'm > upgrading the > current sles8 server I use for that to sles9. I get this message: > > vadnais:~ # mount -t nfs > gsop23nnn09:/cd_images/SLES9/sles9root /sles9root > nfs server reported tcp not available, falling back to udp > Using NFS over UDP can cause data corruption. > > Does this mean something is scrozzled on the system I'm > mounting it on, or > something is scrozzled on the server where the sles9root > exists. I am at a > loss to explain why it is saying TCP is unavailable since I > can access both > of those images. I get that message all the time, with no particular problems. Originally NFS only used UDP for communications. I guess there is now an option to allow NFS to use TCP transport as well. Your system is set up to use the new TCP communications method with fall back to UDP. So it is telling you about the fall back. I don't know how to tell the NFS server to use TCP as well as UDP. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Getting an odd message when trying to NFS mount the sles9root tree
I have to make a new SLES9 installation server because I'm upgrading the current sles8 server I use for that to sles9. I get this message: vadnais:~ # mount -t nfs gsop23nnn09:/cd_images/SLES9/sles9root /sles9root nfs server reported tcp not available, falling back to udp Using NFS over UDP can cause data corruption. Does this mean something is scrozzled on the system I'm mounting it on, or something is scrozzled on the server where the sles9root exists. I am at a loss to explain why it is saying TCP is unavailable since I can access both of those images. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
