Re: NFS problem
Marcy, I was getting ICMP type:03 and code:0D on that datagram - the
"last-datagram" being sent first in the tcpdump.
Let us know if 1024(rsize/wsize) want around the problem.
|-+--->
| | Marcy Cortes|
| | <[EMAIL PROTECTED]|
| | sfargo.com> |
| | Sent by: Linux on |
| | 390 Port|
| | <[EMAIL PROTECTED]|
| | .edu> |
| | |
| | |
| | 08/20/2005 02:44 PM |
| | Please respond to |
| | Linux on 390 Port |
| | |
|-+--->
>--|
|
|
| To: LINUX-390@vm.marist.edu
|
| cc: (bcc: Eddie Chen/SIAC)
|
| Subject: Re: NFS problem
|
>--|
Are you talking about rsize and wsize on the mount command? Or
something else?
Marcy Cortes
(415) 243-6343
"This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Eddie Chen
Sent: Saturday, August 20, 2005 8:25 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] NFS problem
I have this problem in the past... what I did was reduce the bklsize to
1024. Do the tcpdump and get a trace of it.
My problem was that a router cannot handle the way the data was
sent(last data first ).
In the trace your most likely to see the last data being sent
first...
and you will also get ICMP message on this datagram
again set the size less than 1500 and do a traceroute and tcpdump.
|-+--->
| | Marcy Cortes|
| | <[EMAIL PROTECTED]|
| | sfargo.com> |
| | Sent by: Linux on |
| | 390 Port|
| | <[EMAIL PROTECTED]|
| | .edu> |
| | |
| | |
| | 08/20/2005 10:52 AM |
| | Please respond to |
| | Linux on 390 Port |
| | |
|-+--->
>---
---|
|
|
| To: LINUX-390@vm.marist.edu
|
| cc: (bcc: Eddie Chen/SIAC)
|
| Subject: NFS problem
|
>---
---|
Anyone have an ideal what could cause this? This is from my WebSphere
guy.
"I have to use an NFS mount to mount a remote directory from my group's
depot server, which has a share set up on the requisite file system.
So, I issue the command as follows:
mount -t nfs
hisservername.win.wellsfargo.com:/export/depot/WebSphere/5.1 /mnt
Subsequent to this, my session completely hangs.
So, I started issuing this command in the back ground mode, by suffixing
an ampersand ('&'). This prevents my session from hanging, but still
does not complete the NFS mount. However, the process that performs the
mount, just sits there forever.
I then discovered that by issuing a kill on the process that is
performing the mount, the mount does happen, and the process goes away.
Today, on the lnxe8194 server, issuing a kill also did not help the
first time. However, upon repeating the above steps the second time, the
NFS mount succeeded."
This is SLES8, 31bit, current maintenance (SP4+)
Marcy Cortes
"This message may contain confidential and/or privileged information.
If you a
Re: NFS problem
Marcy Cortes wrote: Anyone have an ideal what could cause this? This is from my WebSphere guy. "I have to use an NFS mount to mount a remote directory from my group's depot server, which has a share set up on the requisite file system. So, I issue the command as follows: mount -t nfs hisservername.win.wellsfargo.com:/export/depot/WebSphere/5.1 /mnt Subsequent to this, my session completely hangs. - SNIP This may have something to do with NFS foreground and background mounts. I think you were almost there, trying to put the mount progress int he background, but what you are looking for is the "bg" option to your mount command. It's been a wile since I've worked with NFS, but I do remember having to mount NFS filesystems with the bg option to keep the client machine from becoming blocked on I/O when the source was unavailable or slow. HTH, Wayne -- 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: NFS problem
Yest. but that will not fix the real the problem(you will get a successful
mount)... you need to do a trrace on it.
|-+--->
| | Marcy Cortes|
| | <[EMAIL PROTECTED]|
| | sfargo.com> |
| | Sent by: Linux on |
| | 390 Port|
| | <[EMAIL PROTECTED]|
| | .edu> |
| | |
| | |
| | 08/20/2005 02:44 PM |
| | Please respond to |
| | Linux on 390 Port |
| | |
|-+--->
>--|
|
|
| To: LINUX-390@vm.marist.edu
|
| cc: (bcc: Eddie Chen/SIAC)
|
| Subject: Re: NFS problem
|
>--|
Are you talking about rsize and wsize on the mount command? Or
something else?
Marcy Cortes
(415) 243-6343
"This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Eddie Chen
Sent: Saturday, August 20, 2005 8:25 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] NFS problem
I have this problem in the past... what I did was reduce the bklsize to
1024. Do the tcpdump and get a trace of it.
My problem was that a router cannot handle the way the data was
sent(last data first ).
In the trace your most likely to see the last data being sent
first...
and you will also get ICMP message on this datagram
again set the size less than 1500 and do a traceroute and tcpdump.
|-+--->
| | Marcy Cortes|
| | <[EMAIL PROTECTED]|
| | sfargo.com> |
| | Sent by: Linux on |
| | 390 Port|
| | <[EMAIL PROTECTED]|
| | .edu> |
| | |
| | |
| | 08/20/2005 10:52 AM |
| | Please respond to |
| | Linux on 390 Port |
| | |
|-+--->
>---
---|
|
|
| To: LINUX-390@vm.marist.edu
|
| cc: (bcc: Eddie Chen/SIAC)
|
| Subject: NFS problem
|
>---
---|
Anyone have an ideal what could cause this? This is from my WebSphere
guy.
"I have to use an NFS mount to mount a remote directory from my group's
depot server, which has a share set up on the requisite file system.
So, I issue the command as follows:
mount -t nfs
hisservername.win.wellsfargo.com:/export/depot/WebSphere/5.1 /mnt
Subsequent to this, my session completely hangs.
So, I started issuing this command in the back ground mode, by suffixing
an ampersand ('&'). This prevents my session from hanging, but still
does not complete the NFS mount. However, the process that performs the
mount, just sits there forever.
I then discovered that by issuing a kill on the process that is
performing the mount, the mount does happen, and the process goes away.
Today, on the lnxe8194 server, issuing a kill also did not help the
first time. However, upon repeating the above steps the second time, the
NFS mount succeeded."
This is SLES8, 31bit, current maintenance (SP4+)
Marcy Cortes
"This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must
Re: NFS problem
Are you talking about rsize and wsize on the mount command? Or
something else?
Marcy Cortes
(415) 243-6343
"This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Eddie Chen
Sent: Saturday, August 20, 2005 8:25 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] NFS problem
I have this problem in the past... what I did was reduce the bklsize to
1024. Do the tcpdump and get a trace of it.
My problem was that a router cannot handle the way the data was
sent(last data first ).
In the trace your most likely to see the last data being sent
first...
and you will also get ICMP message on this datagram
again set the size less than 1500 and do a traceroute and tcpdump.
|-+--->
| | Marcy Cortes|
| | <[EMAIL PROTECTED]|
| | sfargo.com> |
| | Sent by: Linux on |
| | 390 Port|
| | <[EMAIL PROTECTED]|
| | .edu> |
| | |
| | |
| | 08/20/2005 10:52 AM |
| | Please respond to |
| | Linux on 390 Port |
| | |
|-+--->
>---
---|
|
|
| To: LINUX-390@vm.marist.edu
|
| cc: (bcc: Eddie Chen/SIAC)
|
| Subject: NFS problem
|
>---
---|
Anyone have an ideal what could cause this? This is from my WebSphere
guy.
"I have to use an NFS mount to mount a remote directory from my group's
depot server, which has a share set up on the requisite file system.
So, I issue the command as follows:
mount -t nfs
hisservername.win.wellsfargo.com:/export/depot/WebSphere/5.1 /mnt
Subsequent to this, my session completely hangs.
So, I started issuing this command in the back ground mode, by suffixing
an ampersand ('&'). This prevents my session from hanging, but still
does not complete the NFS mount. However, the process that performs the
mount, just sits there forever.
I then discovered that by issuing a kill on the process that is
performing the mount, the mount does happen, and the process goes away.
Today, on the lnxe8194 server, issuing a kill also did not help the
first time. However, upon repeating the above steps the second time, the
NFS mount succeeded."
This is SLES8, 31bit, current maintenance (SP4+)
Marcy Cortes
"This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."
--
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
-
This message and its attachments may contain privileged and
confidential information. If you are not the intended recipient(s), you
are prohibited from printing, forwarding, saving or copying this email.
If you have received this e-mail in error, please immediately notify the
sender and delete this e-mail and its attachments from your computer.
--
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: NFS problem
I have this problem in the past... what I did was reduce the bklsize to
1024. Do the tcpdump and get a trace of it.
My problem was that a router cannot handle the way the data was sent(last
data first ).
In the trace your most likely to see the last data being sent first...
and you will also get ICMP message on this datagram
again set the size less than 1500 and do a traceroute and tcpdump.
|-+--->
| | Marcy Cortes|
| | <[EMAIL PROTECTED]|
| | sfargo.com> |
| | Sent by: Linux on |
| | 390 Port|
| | <[EMAIL PROTECTED]|
| | .edu> |
| | |
| | |
| | 08/20/2005 10:52 AM |
| | Please respond to |
| | Linux on 390 Port |
| | |
|-+--->
>--|
|
|
| To: LINUX-390@vm.marist.edu
|
| cc: (bcc: Eddie Chen/SIAC)
|
| Subject: NFS problem
|
>--|
Anyone have an ideal what could cause this? This is from my WebSphere
guy.
"I have to use an NFS mount to mount a remote directory from
my group's depot server, which has a share set up on the requisite file
system.
So, I issue the command as follows:
mount -t nfs
hisservername.win.wellsfargo.com:/export/depot/WebSphere/5.1 /mnt
Subsequent to this, my session completely hangs.
So, I started issuing this command in the back ground mode, by suffixing
an
ampersand ('&'). This prevents my session from hanging, but still does
not
complete the NFS mount. However, the process that performs the mount,
just sits there forever.
I then discovered that by issuing a kill on the process that is
performing
the mount, the mount does happen, and the process goes away.
Today, on the lnxe8194 server, issuing a kill also did not help the
first time. However, upon repeating the above steps the second time,
the NFS mount succeeded."
This is SLES8, 31bit, current maintenance (SP4+)
Marcy Cortes
"This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."
--
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
-
This message and its attachments may contain privileged and confidential
information. If you are not the intended recipient(s), you are prohibited
from printing, forwarding, saving or copying this email. If you have
received this e-mail in error, please immediately notify the sender and
delete this e-mail and its attachments from your computer.
--
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
NFS problem
Anyone have an ideal what could cause this? This is from my WebSphere
guy.
"I have to use an NFS mount to mount a remote directory from
my group's depot server, which has a share set up on the requisite file
system.
So, I issue the command as follows:
mount -t nfs
hisservername.win.wellsfargo.com:/export/depot/WebSphere/5.1 /mnt
Subsequent to this, my session completely hangs.
So, I started issuing this command in the back ground mode, by suffixing
an
ampersand ('&'). This prevents my session from hanging, but still does
not
complete the NFS mount. However, the process that performs the mount,
just sits there forever.
I then discovered that by issuing a kill on the process that is
performing
the mount, the mount does happen, and the process goes away.
Today, on the lnxe8194 server, issuing a kill also did not help the
first time. However, upon repeating the above steps the second time,
the NFS mount succeeded."
This is SLES8, 31bit, current maintenance (SP4+)
Marcy Cortes
"This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."
--
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: NFS PROBLEM
I was pointing to the wrong directory. I mounted the right directory and it tested ok. Thanx moloko > -Original Message- > From: Harald Hoyer [SMTP:[EMAIL PROTECTED]] > Sent: 05 February 2002 13:11 > To: [EMAIL PROTECTED] > Subject: Re: NFS PROBLEM > > ftp.redhat.de/pub/s390-7.2/SRPMS is the directory with the source code > packages... :-) > try the directory with a RedHat dir inside... > > On Tue, Feb 05, 2002 at 08:01:21AM +0200, Moloko Monyepao wrote: > > I can manually mount an NFS file on my linux system but as soon I > run > > RHSETUP I get the following error: > > > > Mounting filesystems... > > insmod: a module named loop already exists > > insmod: a module named cramfs already exists > > No Red Hat directory structure found. > > Stopped installation. No cleanup is done! > > > > mount > > > 147.110.52.37:/home/ftp/pub/linux/redhat7.2_OS390/ftp.redhat.de/pub/s3 > 90 > > -7.2/SRPMS /install works ok. > > > > Please assist > > moloko > > -- > Harald Hoyer, Software Developer Tel. : +49-711-96437-0 > Red Hat GmbH Fax. : +49-711-96437-111 > Hauptstaetterstr. 58 Email: [EMAIL PROTECTED] > D-70178 Stuttgart Web : http://www.redhat.de/
Re: NFS PROBLEM
ftp.redhat.de/pub/s390-7.2/SRPMS is the directory with the source code packages... :-) try the directory with a RedHat dir inside... On Tue, Feb 05, 2002 at 08:01:21AM +0200, Moloko Monyepao wrote: > I can manually mount an NFS file on my linux system but as soon I run > RHSETUP I get the following error: > > Mounting filesystems... > insmod: a module named loop already exists > insmod: a module named cramfs already exists > No Red Hat directory structure found. > Stopped installation. No cleanup is done! > > mount > 147.110.52.37:/home/ftp/pub/linux/redhat7.2_OS390/ftp.redhat.de/pub/s390 > -7.2/SRPMS /install works ok. > > Please assist > moloko -- Harald Hoyer, Software Developer Tel. : +49-711-96437-0 Red Hat GmbH Fax. : +49-711-96437-111 Hauptstaetterstr. 58 Email: [EMAIL PROTECTED] D-70178 Stuttgart Web : http://www.redhat.de/
Re: NFS PROBLEM
You must point it to the the directory where RedHat/ lives since it uses the RedHat/base and RedHat/RPMS directories. It does not use the SRPMS directory. Rob
NFS PROBLEM
I can manually mount an NFS file on my linux system but as soon I run RHSETUP I get the following error: Mounting filesystems... insmod: a module named loop already exists insmod: a module named cramfs already exists No Red Hat directory structure found. Stopped installation. No cleanup is done! mount 147.110.52.37:/home/ftp/pub/linux/redhat7.2_OS390/ftp.redhat.de/pub/s390 -7.2/SRPMS /install works ok. Please assist moloko
