In response to Lucas Wang lw...@us.toyota-itc.com:
We use NFS to store /home directory for users in our lab.
However, we occasionally get blocked from logging in because
the automount daemon on a NFS client machine hangs. When
that happens, we get this error message on the NFS client
Hi--
Janos Dohanics wrote:
I have a FreeBSD 4.11 machine which mounts a volume from a Netapp ONTap.
The FreeBSD machine also acts as a Samba PDC. The Samba volumes are in
the NFS-mounted volume. There are about a dozen Win2K workstations on
the network served by the Samba server.
Lately I have
At 10:55 AM 5/3/2007, you wrote:
Hi--
Janos Dohanics wrote:
I have a FreeBSD 4.11 machine which mounts a volume from a Netapp ONTap.
The FreeBSD machine also acts as a Samba PDC. The Samba volumes are in
the NFS-mounted volume. There are about a dozen Win2K workstations on
the network served
Jonathan Horne wrote:
updated my NFS server to 6.2-RELEASE last night. today, i find that
freebsd
or linux clinets alike, are all getting:
athena:/usr/src: RPCPROG_MNT: RPC: Timed out
i cant think of what to check. the nfs server has this in the
/etc/rc.conf:
rpcbind_enable=YES
On 1/13/07, Jay Chandler [EMAIL PROTECTED] wrote:
Jonathan Horne wrote:
updated my NFS server to 6.2-RELEASE last night. today, i find that
freebsd
or linux clinets alike, are all getting:
athena:/usr/src: RPCPROG_MNT: RPC: Timed out
i cant think of what to check. the nfs server has
On Saturday 13 January 2007 17:47, Jonathan Horne wrote:
On 1/13/07, Jay Chandler [EMAIL PROTECTED] wrote:
Jonathan Horne wrote:
updated my NFS server to 6.2-RELEASE last night. today, i find that
freebsd
or linux clinets alike, are all getting:
athena:/usr/src: RPCPROG_MNT:
DSA - JCR wrote:
I have read it and downloaded, but it seems to be something obsolete (v.
3.5 is from 2004) and I suspect they hasn't made nothing new.
It supports NFSv3 and TCP mounts which (right now) is all you want.
We'll see if MS start to support NFSv4, but right now, IIRC, even BSD
I am mounting a NFS server (FreeBSD 6.1 amd64) for a MS Windows Network
for a customer and I see that I can not see the NFS server from windows
boxes.
Must I install Samba for that? or anything in the MS Windows boxes?
I thougth that Windows understand NFS but seems to be not.
I've
HI all and thanks for your answers
My main goal is to have a system in which the local network can get access
to the file repository, and also thay can get access from their homes to
them (only get a file from server, work on it, and post it to the server).
For this reason I thougth in NFS only
Can I have the two? NFS and Samba?
There is no reason you can't.
I run NFS between Unix machines and Samba with MS world.
But there could be strange results if on Xp machines connects to the
same file using both NFS and Samba at same time.
Olivier
On Jun 20, 2006, at 2:04 AM, Olivier Nicole wrote:
Can I have the two? NFS and Samba?
There is no reason you can't.
I run NFS between Unix machines and Samba with MS world.
But there could be strange results if on Xp machines connects to the
same file using both NFS and Samba at same time.
DSA - JCR wrote:
Hi all
I am mounting a NFS server (FreeBSD 6.1 amd64) for a MS Windows Network
for a customer and I see that I can not see the NFS server from windows
boxes.
Must I install Samba for that? or anything in the MS Windows boxes?
I thougth that Windows understand NFS but seems to
On Mon, June 19, 2006 9:17 pm, DSA - JCR wrote:
Hi all
I am mounting a NFS server (FreeBSD 6.1 amd64) for a MS Windows Network
for a customer and I see that I can not see the NFS server from windows
boxes.
Must I install Samba for that? or anything in the MS Windows boxes?
I thougth that
DSA - JCR wrote:
Hi all
I am mounting a NFS server (FreeBSD 6.1 amd64) for a MS Windows Network
for a customer and I see that I can not see the NFS server from windows
boxes.
Must I install Samba for that? or anything in the MS Windows boxes?
I thougth that Windows understand NFS but
On Mon, Jun 19, 2006, DSA - JCR wrote:
Hi all
I am mounting a NFS server (FreeBSD 6.1 amd64) for a MS Windows Network
for a customer and I see that I can not see the NFS server from windows
boxes.
Must I install Samba for that? or anything in the MS Windows boxes?
I thougth that Windows
On 19 jun 2006, at 22:17, DSA - JCR wrote:
Hi all
I am mounting a NFS server (FreeBSD 6.1 amd64) for a MS Windows
Network
for a customer and I see that I can not see the NFS server from
windows
boxes.
Must I install Samba for that? or anything in the MS Windows boxes?
I thougth that
On Jun 19, 2006, at 3:38 PM, FBSD_UG wrote:
On 19 jun 2006, at 22:17, DSA - JCR wrote:
Must I install Samba for that? or anything in the MS Windows boxes?
I thougth that Windows understand NFS but seems to be not.
Windows doesn't understand NFS; this is almost purely a Unix
creation. I
David Kirchner wrote:
We recently replaced FreeBSD 4.5 with 6.0-RELEASE on a pair of servers.
One of the servers runs rsync to copy its contents to the other server,
over a NFS mount. Everything worked just fine under 4.5, but with 6.0,
we're seeing dozens of these errors every rsync:
May 2
David Kirchner [EMAIL PROTECTED] wrote:
We recently replaced FreeBSD 4.5 with 6.0-RELEASE on a pair of servers.
One of the servers runs rsync to copy its contents to the other server,
over a NFS mount. Everything worked just fine under 4.5, but with 6.0,
we're seeing dozens of these errors
Michael,
If /usr/local/www is not a mount point, this will not work. You need to
put the mount point (eg: /usr) in /etc/exports, and add the option
-alldirs to allow it to mount a subdirectory of the mount point.
Andrew
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Michael P. Soulier (msoulier) writes:
Hello,
I'm configuring nfsd on my freebsd box, and trying to mount from my
linux box. I keep getting permission denied on the linux side, and I'm
not sure why.
My local network is 192.168.1.0/24.
I've added this to /etc/exports.
/usr/local/www
On 1/6/06, Michael Landin Hostbaek [EMAIL PROTECTED] wrote:
Look alright.
After adding the line to /etc/exports - mountd(8) needs to re-read the
file. So do:
# kill -s HUP `cat /var/run/mountd.pid`
You can also use 'showmount -e' to see the configured exports list.
Hmm. I restarted nfsd,
On 1/6/06, Webster, Andrew [EMAIL PROTECTED] wrote:
Michael,
If /usr/local/www is not a mount point, this will not work. You need to
put the mount point (eg: /usr) in /etc/exports, and add the option
-alldirs to allow it to mount a subdirectory of the mount point.
It would appear that my
On 6 Jan 2006, at 16:33, Michael P. Soulier wrote:
On 1/6/06, Webster, Andrew [EMAIL PROTECTED] wrote:
Michael,
If /usr/local/www is not a mount point, this will not work. You
need to
put the mount point (eg: /usr) in /etc/exports, and add the option
-alldirs to allow it to mount a
On Thu, Dec 29, 2005 at 11:19:10AM +0100, Angel Blazquez wrote:
Hello,
We are expecting incredible overload in a NFS server. A top shows nfsd
consuming most of the CPU:
PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND
6000 root -80 1204K 660K
Am Freitag, 10. Juni 2005 09:51 schrieb Osmany Guirola Cruz:
Hi people
I have installed a 5.3 STABLE box with automount(amd) daemon working
perfectly with the defaults flags(/net /host) and the nfs server
exporting only my home. all this work but then i upgrade my system
to 5.4 and
I am using -stable and i do the upgrade via CTM
in the freebsd site the last ctm is src-5.0393.gz 06/09/05
i hope that with this was sufficient to solve the problem ;-)
this are the affected file with the ctm file 92 and 93
FS .ctm_status
FN contrib/tcpdump/print-bgp.c
FN
Am Freitag, 10. Juni 2005 10:32 schrieb Osmany Guirola Cruz:
I am using -stable and i do the upgrade via CTM
in the freebsd site the last ctm is src-5.0393.gz 06/09/05
i hope that with this was sufficient to solve the problem ;-)
this are the affected file with the ctm file 92 and 93
FS
:-)
I have many restrictions in my network and i can't use cvs or cvsup to
update my port or src tree :-( the only way it's CTM fortunally it
exists i hope that never disapear...
___
freebsd-questions@freebsd.org mailing list
Alex de Kruijff [EMAIL PROTECTED] wrote:
On Mon, Oct 04, 2004 at 12:22:30AM -0300, Marc G. Fournier wrote:
I'm using an nfs mount to get at the underlying file system on a system
that uses unionfs mounts ... instead of using nullfs, which, last time I
used it over a year ago, caused
On Tue, 5 Oct 2004, Alex de Kruijff wrote:
I think you're problem is not that you disk is used havely but that
you're NIC (rsync kinda does that) is. The warnings you get indicate
that you're computer can't get a responce from you're server. It acts
normaly as soon as it can.
Except, the nfs
On Tue, 5 Oct 2004, Bill Moran wrote:
What kind of network topology is between the two machines? Do you
notice a high load on the hub/switch/routers during these activities?
You may be able to improve the intervening network topology to improve
the problem as well.
My bad ... I thought i had
Marc G. Fournier [EMAIL PROTECTED] wrote:
On Tue, 5 Oct 2004, Bill Moran wrote:
What kind of network topology is between the two machines? Do you
notice a high load on the hub/switch/routers during these activities?
You may be able to improve the intervening network topology to
On Tue, 5 Oct 2004, Bill Moran wrote:
Marc G. Fournier [EMAIL PROTECTED] wrote:
On Tue, 5 Oct 2004, Bill Moran wrote:
What kind of network topology is between the two machines? Do you
notice a high load on the hub/switch/routers during these activities?
You may be able to improve the intervening
On Mon, Oct 04, 2004 at 12:22:30AM -0300, Marc G. Fournier wrote:
I'm using an nfs mount to get at the underlying file system on a system
that uses unionfs mounts ... instead of using nullfs, which, last time I
used it over a year ago, caused the server to crash to no end ...
But, as
** Reply to note from adp [EMAIL PROTECTED] Mon, 31 May 2004 12:33:24 -0500
I was thinking that
since NFS is udp-based, that if the primary NFS server failed, and the
secondary assumed the primary NFS server's IP address, that things would at
least return to normal (of course, any writes
On Sun, May 30, 2004 at 02:43:37AM -0500, adp wrote:
I am running a FreeBSD 4.9-REL NFS server. Once every several hours our main
NFS server replicates everything to a backup FreeBSD NFS server. We are okay
with the gap in time between replication. What we aren't sure about is how
to automate
adp wrote:
One of my big problems right now is that if our primary NFS server goes down
then everything using that NFS mount locks up. If I change to the mounted
filesystem on the client then it stalls:
# pwd
/root
# cd /nfs-mount-dir
[locks]
If I try to reboot the reboot fails as well since
We can live with the chance that a file write might fail as long as we can
switch over to another NFS server if the primary fails. So amd will help us
avoid the client hung issue? I will have to take a look. That is the worst
thing of all when it comes to a failed NFS server. You can't even
-
From: Chuck Swiger [EMAIL PROTECTED]
To: adp [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 11:55 AM
Subject: Re: NFS server fail-over - how do you do it?
adp wrote:
One of my big problems right now is that if our primary NFS server goes
down
then everything using
adp wrote:
We can live with the chance that a file write might fail as long as we can
switch over to another NFS server if the primary fails.
Sorry, NFS simply won't work with the model of operation you've described.
There is no way to do fallback to a secondary NFS server if the primary goes
In the last episode (May 31), adp said:
Very useful information, thanks. We have a very stable NFS server,
but I am still working hard to put some redundancy into place. I was
thinking that since NFS is udp-based, that if the primary NFS server
failed, and the secondary assumed the primary NFS
Couple of issues regarding failover.
1) If system B is going to take over system a's IP,
it also needs to take it's MAC address. Else you
have to wait for an ARP timeout.
Some systems (all?) perform a gratuitous arp-reply
when an if comes up. But some other systems ignore
this
On Sun, 30 May 2004 02:43:37 -0500
adp [EMAIL PROTECTED] wrote:
I am running a FreeBSD 4.9-REL NFS server. Once every several hours our main
NFS server replicates everything to a backup FreeBSD NFS server. We are okay
with the gap in time between replication. What we aren't sure about is how
On Sun, 30 May 2004 02:43:37 -0500
adp [EMAIL PROTECTED] wrote:
Just curious how this problem is being solved.
I cant say i've ever looked into it myself but id susjest an easy solution would be to
have a cron script store run every now and again to ping the servers and change the
mounts
One of my big problems right now is that if our primary NFS server goes down
then everything using that NFS mount locks up. If I change to the mounted
filesystem on the client then it stalls:
# pwd
/root
# cd /nfs-mount-dir
[locks]
If I try to reboot the reboot fails as well since FreeBSD can't
Charles Swiger wrote:
On Feb 26, 2004, at 4:57 PM, Michael Conlen wrote:
[ ... ]
The production system will use dual channel U320 RAID controllers
with 12 disks per channel, so disk shouldn't be an issue, and it will
connect with GigE, so network is plenty fine, now I'm on to CPU.
Sounds
On Feb 26, 2004, at 2:30 PM, Michael Conlen wrote:
Does FreeBSD's NFS implementation allow for caching of documents on
the client side, either its self or through the VM system's inactive
pages?
Yes to both. NFS clients typically use something called biod or
nfsoid, which implements some
On Feb 26, 2004, at 4:33 PM, Charles Swiger wrote:
Well, you are going to be bottlenecked potentially by your network or
by the maximum I/O rate that your NFS server can sustain. Your data
suggests you ought to be able to handle about two orders of magnitude
more net traffic, if you're over a
On Feb 26, 2004, at 4:57 PM, Michael Conlen wrote:
[ ... ]
The production system will use dual channel U320 RAID controllers with
12 disks per channel, so disk shouldn't be an issue, and it will
connect with GigE, so network is plenty fine, now I'm on to CPU.
Sounds like you've gotten nice
On Tue, Sep 30, 2003 at 09:10:23AM -0400, stan wrote:
I'm having a bit of a problem using a FeeBSD STABLE machine as an NFS
server for an HP-UXa box. I'm able to mount the FreeBSD box, abd see the
files, but take a look at this:
...
So, I'm thinking that I've got a problem with files 2G Does
On Tue, 30 Sep 2003 22:40, stan wrote:
I'm having a bit of a problem using a FeeBSD STABLE machine as an NFS
server for an HP-UXa box. I'm able to mount the FreeBSD box, abd see the
files, but take a look at this:
On teh FreeBSD machine
$ ls -l
total 11471104
-rw-rw-r-- 1 stan wheel
On Tue, Sep 30, 2003 at 09:10:23AM -0400, stan wrote:
Same place seen from the HP-UX machine
$ ls -l
total 45884416
-rw-rw-r-- 1 1004 root 3153586176 Sep 24 08:34 oracle_dump.09242003
So, I'm thinking that I've got a problem with files 2G Does this make
sense?
Yep, and it's
Guy Van Sanden [EMAIL PROTECTED] writes:
Does anyone know if and how it is possible to set up a redundant NFS server?
Somthing like that is expensive and mostly not needed. Rsync with a
hot standby system is ok. If the mainserver fail, go to the second
and reconfigure the ip interface.
Bis
Hi Matthias
Thank you for your answer.
I think I'll do it that way, I was wondering if it would have been possible, Solaris
supports giving multiple servers when mounting NFS shares, but I couldn't find
something similar on FreeBSD and Linux.
Kind regards
Guy
On Mon, 2003-09-29 at 14:30,
Guy Van Sanden wrote:
[ ... ]
Does anyone know if and how it is possible to set up a redundant NFS server?
Yes, although true redundancy for NFS is available only for read-only shares.
From man mount_nfs under Solaris:
Replicated file systems and failover
resource can list
Guy Van Sanden [EMAIL PROTECTED] writes:
Hi Matthias
Moin,
Thank you for your answer. I think I'll do it that way, I was
wondering if it would have been possible, Solaris supports giving
There isnt any out-of-the-box solution for BSD. You can hack
arround the problem.
multiple servers
[I'm taking this off -stable because it really doesn't belong there]
Hartmann, O. wrote:
On Thu, 10 Oct 2002, Bill Moran wrote:
Hello Bill.
:Hartmann, O. wrote:
: Dear Sirs.
:
: Using FreeBSD 4.6.2-pl2 and FreeBSD 4.7-RC2 on our server system (one 4.7-RC
: experimental system) and
Hartmann, O. wrote:
Dear Sirs.
Using FreeBSD 4.6.2-pl2 and FreeBSD 4.7-RC2 on our server system (one 4.7-RC
experimental system) and utilizing AMD for mounting home space and other
services via TCP protocol results in
nfs server 134.93.180.216:/usr/homes: not responding
nfs server
On Thu, 10 Oct 2002, Bill Moran wrote:
Hello Bill.
:Hartmann, O. wrote:
: Dear Sirs.
:
: Using FreeBSD 4.6.2-pl2 and FreeBSD 4.7-RC2 on our server system (one 4.7-RC
: experimental system) and utilizing AMD for mounting home space and other
: services via TCP protocol results in
:
: nfs server
60 matches
Mail list logo
