On Fri, 11 Sep 2009, Rick Macklem wrote:
I cannot sucessfully mount exports from the NFSv3 server on the
8.0-BETA4 client. All works well with 7.2 clients.
The strange thing is, the directory in which I mount the nfs
filesystem disappears, and I get an error when I attempt to access
I cannot sucessfully mount exports from the NFSv3 server on the
8.0-BETA4 client. All works well with 7.2 clients.
The strange thing is, the directory in which I mount the nfs
filesystem disappears, and I get an error when I attempt to access the
directory.
I went and looked at the
On Fri, 18 Sep 2009, John Marshall wrote:
On Thu, 17 Sep 2009, 21:28 +0300, George Mamalakis wrote:
Dear all,
I am trying to setup ldap with heimdal on my fbsd 8.0-BETA4 and when I
run ldapsearch to see if I can authenticate via GSSAPI I keep getting
the following error:
[r...@ldap root]#
On Fri, 18 Sep 2009, John Marshall wrote:
On Thu, 17 Sep 2009, 21:28 +0300, George Mamalakis wrote:
Dear all,
I am trying to setup ldap with heimdal on my fbsd 8.0-BETA4 and when I
run ldapsearch to see if I can authenticate via GSSAPI I keep getting
the following error:
[r...@ldap root]#
On Fri, 18 Sep 2009, Sam Leffler wrote:
FWIW I hit the same problem (I think) with cyrus imap and saslauthd. I
am running HEAD and tried building w/ and w/o kerberos enabled but
cyradm aborts on startup complaining about the missing symbol. I
started digging because I couldn't get cyrus
On Mon, 21 Sep 2009, George Mamalakis wrote:
[stuff snipped]
SUCCESS!
So, this fix obviates THAT reason for installing the Heimdal port. If
George meets with similar success adding -lgssapi_spnego for his spnego
problem, I suggest that both libraries be added to the list in line 96
of
On Mon, 21 Sep 2009, Peter Ankerstål wrote:
Could this be the same problem I have with SASL and postfix?
http://lists.freebsd.org/pipermail/freebsd-questions/2009-September/205525.html
I have no idea, but there's one way to find out. Apply this patch to
/usr/bin/krb5-config and then
On Sun, 27 Sep 2009, Robert Watson wrote:
On Fri, 25 Sep 2009, Jamie Gritton wrote:
It seems to be NFS related. I think the null pointer in question is from
the export's anonymous credential. Try the patch below and see if it helps
(which I guess means run it overnight and see if it
First off, I know that cross posting is evil, but I wanted to try
and make sure developers saw it.
On Tue, 27 Oct 2009, Olaf Seibert wrote:
I see an annoying behaviour with NFS over TCP. It happens both with nfs
and newnfs. This is with FreeBSD/amd64 8.0-RC1 as client. The server is
some
On Thu, 29 Oct 2009, Olaf Seibert wrote:
After writing, I realised that it is indeed perfectly allowed for the
client to send data. But since the server already sent its FIN, it can't
send anything more, not even an error message. So with that in mind, the
client shouldn't send anything any
On Thu, 29 Oct 2009, Olaf Seibert wrote:
Thanks, it looks like it should do the trick. I can't try it before
monday, though.
Although I think the patch does avoid sending the request on the
partially closed connection, it doesn't fix the real problem,
so I don't know if it is worth
On Mon, 2 Nov 2009, Olaf Seibert wrote:
Although I think the patch does avoid sending the request on the
partially closed connection, it doesn't fix the real problem,
so I don't know if it is worth testing?
Well, I tested it anyway, just in case. It seems to work fine for me, so
far.
Yes,
On Tue, 27 Oct 2009, Olaf Seibert wrote:
I see an annoying behaviour with NFS over TCP. It happens both with nfs
and newnfs. This is with FreeBSD/amd64 8.0-RC1 as client. The server is
some Linux or perhaps Solaris, I'm not entirely sure.
[good stuff snipped...]
Though technically the
On Fri, 20 Nov 2009, Gerrit K??hn wrote:
Hi all,
I have a 8.0-PRERELEASE zfs/nfs server here that complains about i/o
errors when using rsync on a nfs client:
rsync: mkstemp
/usr/portage/metadata/cache/app-mobilephone/.ksms-0.1.2.4.BynVFw failed:
Input/output error (5)
I found this to be
On Mon, 14 Dec 2009, Jeremie Le Hen wrote:
Hi,
__ Please Cc: me when replying as I'm not subscribed. Thanks. __
My NFS server is running FreeBSD 8.0 from December 6th. The client is a
NetBSD 5.0. The directory exported is /data/repos on the server
(192.168.1.222) and is mounted on
On Mon, 14 Dec 2009, Jeremie Le Hen wrote:
00:00:01.953196 IP (tos 0x0, ttl 64, id 48966, offset 0, flags [none], proto UDP
(17), length 168) 192.168.1.1.3819288094 192.168.1.222.2049: 140 readdir
[|nfs]
00:00:01.953665 IP (tos 0x0, ttl 64, id 27028, offset 0, flags [+], proto UDP
(17),
On Tue, 29 Dec 2009, Jeremie Le Hen wrote:
[stuff snipped]
This appears to be the reply to the nfs readdir request, which is what
would be expected. It could be a problem with the content or the reply
or a NetBSD client issue.
If you were to email me the raw tcpdump capture for the above, I
On Sat, 2 Jan 2010, Jeremie Le Hen wrote:
I will reduce the MTU and see if the problem arises with directories
that could be read correctly otherwise. I will keep you informed.
You can reduce rsize to 1024, so that it isn't happening, but that
will also change the size of the readdir
On Wed, 6 Jan 2010, alan bryan wrote:
I have a AMD64 FreeBSD 8.0 server with ZFS filesystem being shared via NFS.
These are being accessed by the clients. The clients are a mix of FreeBSD 6.2
32bit and FreeBSD 7.0 64bit. I have seen similar behavior from both versions
of FreeBSD as
On Wed, 6 Jan 2010, alan bryan wrote:
I have a AMD64 FreeBSD 8.0 server with ZFS filesystem being shared via NFS.
These are being accessed by the clients. The clients are a mix of FreeBSD 6.2
32bit and FreeBSD 7.0 64bit. I have seen similar behavior from both versions
of FreeBSD as
On Fri, 22 Jan 2010, Mikolaj Golub wrote:
We have nonempty nm_bufq, nm_bufqiods = 1, but actually there is no nfsiod
thread run for this mount, which is wrong -- nm_bufq will not be emptied until
some other process starts writing to the nfsmount and starts nfsiod thread for
this mount.
On Fri, 22 Jan 2010, Rick Macklem wrote:
There should probably be some sort of 3 way handshake between
the code in nfs_asyncio() after calling nfs_nfsnewiod() and the
code near the beginning of nfssvc_iod(), but I think the following
somewhat cheesy fix might do the trick:
[stuff deleted
On Sat, 23 Jan 2010, Mikolaj Golub wrote:
I applied your patch to FreeBSD8.0 (the box I get on weekend :-), mounted 10
shares, set vfs.nfs.iodmaxidle=10 (to have nfsiod creation more frequently)
and have been running tests for 4 hours -- just to check the patch does not
break anything. No
On Mon, 1 Feb 2010, John Baldwin wrote:
I'd say that your patch works.
John, are you okay with that patch?
http://people.freebsd.org/~marius/fha_extract_info_realign2.diff
It's intention is to:
- Move nfs_realign() from the NFS client to the shared NFS code and
remove the NFS server
On Tue, 2 Feb 2010, alan bryan wrote:
--- On Wed, 1/6/10, Rick Macklem rmack...@uoguelph.ca wrote:
From: Rick Macklem rmack...@uoguelph.ca
Subject: Re: Zombie NFS writing from FreeBSD clients to FreeBSD 8.0 server with
ZFS
To: alan bryan alan.br...@yahoo.com
Cc: freebsd-stable@freebsd.org
On Fri, 5 Feb 2010, George Mamalakis wrote:
Dear all,
I am running FBSD8-STABLE on an nfsv3 server and an nfsv3 client. My
configuration is based on
http://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup. My goal is
to share filesystems securely through kerberos authentication.
On Fri, 5 Feb 2010, George Mamalakis wrote:
shows no tickets. This could be also a security threat, in case different
kerberos principals (users in this setup) use a shared machine account to
logon, and then access their resources by kiniting to their respective
principals.
The kernel
On Fri, 5 Feb 2010, George Mamalakis wrote:
I assume that this must have to do with kernel's KGSSAPI support, which
forgets to delete or renew its kerberos' cache.
Oops, missed this on the last reply. It is actually a cache of handles
for RPCSEC_GSS credentials allocated by the server
On Sat, 6 Feb 2010, George Mamalakis wrote:
thank you for all your answers. I am planning on setting up the computer labs
of my department using kerberized nfsv3 (since v4 seems to be more
experimental) with a FreeBSD nfs server and Linux nfs clients. I was
wondering how stable such an
On Mon, 8 Feb 2010, O. Hartmann wrote:
Mounting the filessystem via
mount_newnfs host:/path /path
works fine, but not
mount -t nfs4 host:/path /path.
The mount command can be either:
mount -t nfs -o nfsv4 host:/path /path
or
mount -t newnfs -o nfsv4 host:/path /path
(The above was what
On Mon, 8 Feb 2010, O. Hartmann wrote:
Mounting the filessystem via
mount_newnfs host:/path /path
Oh, and you should set:
sysctl vfs.newnfs.locallocks_enable=0
in the server, since I haven't fixed the local locking yet. (This implies
that apps/daemons running locally on the server
On Mon, 8 Feb 2010, O. Hartmann wrote:
Oh, and you should set:
sysctl vfs.newnfs.locallocks_enable=0
in the server, since I haven't fixed the local locking yet. (This implies
that apps/daemons running locally on the server won't see byte range
locks performed by NFSv4 clients.) However,
On Mon, 8 Feb 2010, O. Hartmann wrote:
So I guess the above one is the more 'transparent' one with respect to the
future, when NFSv4 gets mature and its way as matured into the kernel?
Yea, I'd only use mount -t newnfs if for some reason you want to
test/use the experimental client for
On Mon, 8 Feb 2010, George Mamalakis wrote:
To tell you the truth, when I recompiled my kernel with:
options NFSD
options KGSSAPI
device crypto
to setup an nvsv4 server, nfsd refused to start because mountd was
segfaulting. I didn't play much with this setup,
On Tue, 9 Feb 2010, O. Hartmann wrote:
Well, I guess I havn't uderstood everything of NFSv4. The 'concept' of the
'root' is new to me, maybe there are some deeper explanation of the purpose?
Are there supposed to be more than one 'root' enries or only one?
Only to specify different
On Thu, 11 Feb 2010, John Baldwin wrote:
[good stuff snipped]
Case1: single currupted block 3779CF88-3779 (12408 bytes).
Data in block is shifted 68 bytes up, loosing first 68 bytes are
filling last 68 bytes with garbage. Interestingly, among that garbage
is my hostname.
Is it the
On Thu, 11 Feb 2010, John Baldwin wrote:
Case1: single currupted block 3779CF88-3779 (12408 bytes).
Data in block is shifted 68 bytes up, loosing first 68 bytes are
filling last 68 bytes with garbage. Interestingly, among that garbage
is my hostname.
Is it the hostname of the server or
On Fri, 12 Feb 2010, Dmitry Marakasov wrote:
I'm planning a massive testing for this weekend, including removing
soft mount option and trying linux client/server.
Btw, I forgot to mention that I'm experiencing other NFS problems from
time to time, including death of a mount (that is, all
On Fri, 12 Feb 2010, Dmitry Marakasov wrote:
Interesting, I'll try disabling it. However now I really wonder why
is such dangerous option available (given it's the cause) at all,
especially without a notice. Silent data corruption is possibly the
worst thing to happen ever.
I doubt that
On Fri, 12 Feb 2010, Dmitry Marakasov wrote:
* Oliver Fromme (o...@lurza.secnetix.de) wrote:
I'm sorry for the confusion ... I do not think that it's
the cause for your data corruption, in this particular
case. I just mentioned the potential problems with soft
mounts because it could
On Thu, 18 Feb 2010, Boris Kochergin wrote:
Ahoy. I didn't get any replies to this on -net, so I thought I'd try here. I
have an 8.0-RELEASE-p2/amd64 machine running a custom kernel (configuration
file at http://acm.poly.edu/~spawk/ACM) and I am unable to use the NFS server
module on it.
On Fri, 19 Feb 2010, Kostik Belousov wrote:
[stuff snipped]
I think this is changed in HEAD, and part of the changes are already in
stable/8, which is different from 8.0 too.
Anyway, for HEAD nfsserver we need 1. nfscommon 2. nfs_common. Also,
nfs_common module is not attached to the build.
On Fri, 19 Feb 2010, Kostik Belousov wrote:
I do not introduce new module, I added symbols from nfs_common to
nfscommon, indending to remove sys/modules/nfs_common from src, since it
is not attached to the build even without the patch. It seems that there
is no name conflicts between newnfs
On Fri, 19 Feb 2010, George Mamalakis wrote:
Hi all,
the title explains it all...
But ok, let's be a bit more extensive.
If I have one line in /etc/exports reading:
V4: / -alldirs
and try to start mountd, it segfaults with signal 11. From the manpage I read
that -alldirs is the second
On Fri, 19 Feb 2010, Kostik Belousov wrote:
It was changed, see sys/nfsclient/nfs_vfsops.c chunk in the patch.
I tested it by mounting localhost:/usr/home over /mnt.
Oops, sorry for the noise. Me being slow again:-) rick
___
On Fri, 19 Feb 2010, George Mamalakis wrote:
question 1)
I want to export my /export directory with -sec=krb5 to my clients, and the
configuration of my server and client is respectively as follows:
- server:
/etc/exports:
V4: / -sec=krb5
/export
You need -sec=krb5 on the /export line
. But TCP is workable as next best.
NFS; Rick Macklem would be a better choice, but as reported, he's MIA.
Not exactly MIA, but only able to read email from time to time at this
point. I don't know when I'll be able to do more than that.
So, it does sound like it is UDP specific. Robert mentioned
On Sat, 27 Feb 2010, al...@ulgsm.ru wrote:
try to mount /exp/distfiles
]mount /exp/distfiles
]
try to write
]touch /exp/distfiles/t
touch: /exp/distfiles/t: Permission denied
ls and read files ok.
When writes fail for me, it's usually a uid, gid vs user/group
name mapping problem.
On Tue, 2 Mar 2010, Daniel Braniss wrote:
runing with the experimental nfs server all is ok!
(at least I can't see any mbuf leakage :-)
so now that we can assume that the problem is in NFS/UDP writes via
classic nfsserver, where to look?
It might also be the krpc reply cache, since the
On Wed, 3 Mar 2010, Daniel Braniss wrote:
disabling the krpc reply cache does it, no visible damage. Somehow
this reminds me of my old 1970 beetle, parts would fall off but it would
continue working :-)
where to go from here?
Ok, so it sounds like the leak is in the krpc reply cache code,
On Thu, 4 Mar 2010, Daniel Braniss wrote:
correct. The interesting side effect, is that I can't see any negative
issues when disabling the cash.
If the client retries a non-idempotent RPC, the server will do it
again, which can result in data corruption. This is likely to happen
On Tue, 2 Mar 2010, Daniel Braniss wrote:
just keep sending insights/pointers and enjoy life
You could try this patch for sys/rpc/replay.c. Completely untested and
just typed into email (so don't give it to patch, just edit the file).
- try adding these 2 lines just before the end of
On Fri, 5 Mar 2010, Daniel Braniss wrote:
On Tue, 2 Mar 2010, Daniel Braniss wrote:
just keep sending insights/pointers and enjoy life
You could try this patch for sys/rpc/replay.c. Completely untested and
just typed into email (so don't give it to patch, just edit the file).
- try
On Sat, 6 Mar 2010, Daniel Braniss wrote:
it works ok in 7.2, so it would be interesting to compare changes ...
The sys/rpc in FreeBSD8 is completely different code than what is used in
FreeBSD7, so I'm afraid thay're apples vs oranges.
rick
___
On Mon, 29 Mar 2010, Jeremy Chadwick wrote:
I can't find a definition of what the acronyms NLM and NSM stand for,
nor does Googling the error messages return relevant results (except one
FreeBSD committer reporting similar, but nobody replied). I don't know
the implications of these
On Mon, 29 Mar 2010, Jeremy Chadwick wrote:
I recently brought up rpc.lockd and rpc.statd on all of our NFS clients
(mixed RELENG_6, RELENG_7, and RELENG_8), and our NFS server (RELENG_8).
All clients had nfs_client_enable=yes in rc.conf prior to their last
reboot, but lacked
On Thu, 15 Apr 2010, Giulio Ferro wrote:
Here's the setup:
server : NFS server machine (fb 8 stable amd64 )
client : NFS client machine (as above)
server and client are both sharing the same permission database through ldap:
Both have in /etc/nsswitch.conf
...
group: files ldap
...
passwd:
On Fri, 16 Apr 2010, Giulio Ferro wrote:
Yes, I have more than 16 groups, 22 actually...
However I still think this might be a NFS problem, since when I login on
the server machine I can access that directory all right, the problem arises
only when I try to access that dir in the client
On Fri, 16 Apr 2010, Giulio Ferro wrote:
On 16.04.2010 10:29, Sean wrote:
Yes, I have more than 16 groups, 22 actually...
Then there's nothing wrong per se, you're just hitting the fact that NFS
v2 and v3 only support 16 groups on the wire. That's just the way the
protocol is defined.
On Fri, 21 May 2010, Mark Morley wrote:
Having an issue with a file server here (7.3-STABLE i386)
The nfsd processes are hanging. Client access to the nfs shares stops working
and the nfsd processes on the server cannot be killed by any means. There are
no errors showing up anywhere on
On Tue, 25 May 2010, Mark Morley wrote:
On Fri, 21 May 2010 11:32:33 -0400 (EDT) Rick Macklem wrote: On Fri, 21 May
2010, Mark Morley wrote:
Having an issue with a file server here (7.3-STABLE i386)
The nfsd processes are hanging. Client access to the nfs shares stops working
On Tue, 25 May 2010, Mark Morley wrote:
On Fri, 21 May 2010 11:32:33 -0400 (EDT) Rick Macklem wrote: On Fri, 21 May
2010, Mark Morley wrote:
Having an issue with a file server here (7.3-STABLE i386)
The nfsd processes are hanging. Client access to the nfs shares stops working
On Wed, 26 May 2010, Mark Morley wrote:
Thanks, but unfortunately it didn't work. Rebooted it four hours ago with the
patch in place and at the moment I have seven nfsd processes stuck in that
state.
Could it indicate a problem with the underlying disk system? It's an aac0
raid, but it
On Sat, 12 Jun 2010, Kostik Belousov wrote:
On Sat, Jun 12, 2010 at 11:56:10AM +0300, Mikolaj Golub wrote:
On Sun, 6 Jun 2010 16:44:43 +0200 Leon Me??ner wrote:
LM Hi,
LM I hope this is not the wrong list to ask. Didn't get any answers on
LM -questions.
LM When you try to do the
On Sat, 12 Jun 2010, Kostik Belousov wrote:
Yes, I hoped that Mikolaj ends up with something similar :). Please note
that this is racy, since we cannot know why usecount is greater then 1.
This might cause the silly rename to kick in some time where it should
not, but the race is rare.
I'd
On Sun, 13 Jun 2010, Dmitry Pryanishnikov wrote:
Hello!
I'm trying to start the experimental NFSv4 server in RELENG_8 w/o
building it into the kernel, as nfsv4(4) suggests:
... or start mountd(8) and nfsd(8) with the ``-e'' option to force use of the
experimental server. The
On Sun, 13 Jun 2010, Kostik Belousov wrote:
My note was not an objection, only a note. Also, when committing, please
add a comment explaining what is going on.
Righto, and my response was just my opinion. I'm assuming Mikolaj is
looking at committing this?
rick
On Fri, 25 Jun 2010, al...@ulgsm.ru wrote:
Hi all.
I tryed setup server for booting diskless hosts from different networks.
In one network booting is ok.
I see thet realtek 8139 pxe can`t load pxeboot file fromi tftp server from
another
network.
By changing options in dhcp server, i
On Sat, 26 Jun 2010, al...@ulgsm.ru wrote:
[stuff snipped]
dhcp seems ok.
[alexs:ul-it13:~]kenv
LINES=24
acpi_load=YES
boot.netif.gateway=10.144.140.1
boot.netif.hwaddr=00:1c:c0:5a:f4:72
boot.netif.ip=10.144.142.78
boot.netif.netmask=255.255.252.0
On Sun, 27 Jun 2010, Rick C. Petty wrote:
First off, many thanks to Rick Macklem for making NFSv4 possible in
FreeBSD!
I recently updated my NFS server and clients to v4, but have since noticed
significant performance penalties. For instance, when I try ls a b c (if
a, b, and c are empty
On Sun, 27 Jun 2010, Rick C. Petty wrote:
Hmm. When I mounted the same filesystem with nfs3 from a different client,
everything started working at almost normal speed (still a little slower
though).
Now on that same host I saw a file get corrupted. On the server, I see
the following:
%
On Sun, 27 Jun 2010, Rick C. Petty wrote:
On Sun, Jun 27, 2010 at 08:04:28PM -0400, Rick Macklem wrote:
Weird, I don't see that here. The only thing I can think of is that the
experimental client/server will try to do I/O at the size of MAXBSIZE
by default, which might be causing a burst
On Mon, 28 Jun 2010, al...@ulgsm.ru wrote:
kernel built with:
options BOOTP # Use BOOTP to obtain IP address/hostname
options BOOTP_NFSROOT # NFS mount root file system using BOOTP info
options BOOTP_NFSV3
Try building a kernel without the above options, but with
On Mon, 28 Jun 2010, Rick C. Petty wrote:
On Mon, Jun 28, 2010 at 12:35:14AM -0400, Rick Macklem wrote:
Being stuck in newnfsreq means that it is trying to establish a TCP
connection with the server (again smells like some networking issue).
snip
Disabling delegations is the next step
On Mon, 28 Jun 2010, Rick C. Petty wrote:
Make sure you don't have multiple entries for the same uid, such as root
and toor both for uid 0 in your /etc/passwd. (ie. get rid of one of
them, if you have both)
Hmm, that's a strange requirement, since FreeBSD by default comes with
both. That
On Mon, 28 Jun 2010, Daniel Braniss wrote:
On Mon, 28 Jun 2010, al...@ulgsm.ru wrote:
kernel built with:
options BOOTP # Use BOOTP to obtain IP address/hostname
options BOOTP_NFSROOT # NFS mount root file system using BOOTP info
options BOOTP_NFSV3
Try building a
On Mon, 28 Jun 2010, Rick C. Petty wrote:
I can try it again with v3 client and v4 server, if you think that's
worthy of pursuit. If it makes any difference, the server's four CPUs are
pegged at 100% (running nice +4 cpu-bound jobs). But that was the case
before I enabled v4 server too.
On Tue, 29 Jun 2010, Ian Smith wrote:
Not wanting to hijack this (interesting) thread, but ..
I have to concur with Rick P - that's rather a odd requirement when each
FreeBSD install since at least 2.2 has come with root and toor (in that
order) in /etc/passwd. I don't use toor, but often
On Tue, 29 Jun 2010, al...@ulgsm.ru wrote:
I think using NFS_ROOT but not the BOOTPxxx options will work around this
or you could test the following patch and see if it helps. (Testing the
patch would be appreciated, since I don't have any way to test across
multiple subnets and it would be
On Mon, 28 Jun 2010, Daniel Braniss wrote:
On Mon, 28 Jun 2010, al...@ulgsm.ru wrote:
kernel built with:
options BOOTP # Use BOOTP to obtain IP address/hostname
options BOOTP_NFSROOT # NFS mount root file system using BOOTP info
options BOOTP_NFSV3
Try building a
On Tue, 29 Jun 2010, al...@ulgsm.ru wrote:
Yes. without BOOTPxxx options boot is fine.
Btw, if you feel like helping out with testing it, I have patches for
this case that modify pxeboot to use NFSv3 instead of NFSv2. The more
testing they get the better. They're at:
On Tue, 29 Jun 2010, Rick C. Petty wrote:
To be fair, I'm not sure this is even a problem. Rick M. only suggested it
as a possibility. I would think that getpwuid() would return the first
match which has always been root. At least that's what it does when
scanning the passwd file; I'm not
On Mon, 28 Jun 2010, Rick C. Petty wrote:
It would be interesting to see if the performance problem exists for
NFSv3 mounts against the experimental (nfsv4) server.
Hmm, I couldn't reproduce the problem. Once I unmounted the nfsv4 client
and tried v3, the jittering stopped. Then I
On Wed, 30 Jun 2010, Ian Smith wrote:
I wondered whether this might be a Linux thing. On my 7.2 system,
% find /usr/src -name *.[ch] -exec grep -Hw getpwuid {} \; file
returns 195 lines, many in the form getpwuid(getuid()), in many base and
contrib components - including id(1), bind,
On Mon, 28 Jun 2010, Rick C. Petty wrote:
On Mon, Jun 28, 2010 at 12:35:14AM -0400, Rick Macklem wrote:
Being stuck in newnfsreq means that it is trying to establish a TCP
connection with the server (again smells like some networking issue).
snip
Disabling delegations is the next step
On Sun, 27 Jun 2010, Rick C. Petty wrote:
First off, many thanks to Rick Macklem for making NFSv4 possible in
FreeBSD!
I recently updated my NFS server and clients to v4, but have since noticed
significant performance penalties. For instance, when I try ls a b c (if
a, b, and c are empty
From: pluknet pluk...@gmail.com
To: freebsd-stable freebsd-stable@freebsd.org
Sent: Friday, July 30, 2010 12:53:08 PM
Subject: umount -f nfs forces to panic
Hi.
This is 8.1 booted from NFS.
I did installworld to NFS on idle system, then it started
to print repeatedly nfs server foo:mp
I'm doing some testing with loading up a new storage server. I have
couple ZFS filesystems exported via NFS over UDP.
I have a client machine (8.1 also) that has mounted those filesystems
along with some test PHP scripts that are doing a ton of
read/write/fstat operations to load it up.
[stuff snipped]
I applied this patch and have been unable to reproduce the hang since.
Rick, Thanks for an awesomely quick response!
This will go into 8-Stable at some point?
I believe so. I'll be away from computers until Aug. 24, so maybe
late Aug. to head and mid-Sept. to stable/8.
Hi all,
I have five front end web servers that all mount their content from the same
server via NFS. If I stress the link on any one of the machines (eg: copy a
large directory with a lot of files to/from the mounted file system) the
client will pause. That is, all processes trying to
hi,
I can't seem to find how to manually remap uid gid information while
using NFS, e.g. something similar to this:
http://www.kernelcrash.com/blog/nfs-uidgid-mapping/2007/09/10/
Is such mapping really unimplemented?
Except for root or all uids, no. There is no generic mapping
Hi. I'm still having problems with NFSv4 being very laggy on one
client.
When the NFSv4 server is at 50% idle CPU and the disks are 1% busy,
I am
getting horrible throughput on an idle client. Using dd(1) with 1 MB
block
size, when I try to read a 100 MB file from the client, I'm getting
Well I wouldn't say well. Every client I've set up has had this
issue,
and somehow through tweaking various settings and restarting nfs a
bunch of
times, I've been able to make it tolerable for most clients. Only one
client is behaving well, and that happens to be the only machine I
On Sun, Aug 29, 2010 at 11:44:06AM -0400, Rick Macklem wrote:
Hi. I'm still having problems with NFSv4 being very laggy on one
client.
When the NFSv4 server is at 50% idle CPU and the disks are 1%
busy,
I am
getting horrible throughput on an idle client. Using dd(1) with 1
The freezes are gone, thankfully, but I often get huge slow-downs:
looking in the logs of the nfs clients I get plenty of:
... kernel: nfs server ...:/path/to/dir: lockd not responding
... kernel: nfs server ...:/path/to/dir: lockd is alive again
If you don't need file locking to work
Hi everyone,
I am experiencing similar issues with newnfs:
1) I have two clients that each get around 0.5MiB/s to 2.6MiB/s
reading
from the NFS4-share on Gbit-Lan
2) Mounting with -t newnfs -o nfsv3 results in no performance gain
whatsoever.
3) Mounting with -t nfs results in
On 07/01/10 15:23, Garrett Cooper wrote:
On Thu, Jul 1, 2010 at 11:51 AM, alan bryanalan.br...@yahoo.com
wrote:
--- On Thu, 7/1/10, Garrett Cooperyanef...@gmail.com wrote:
From: Garrett Cooperyanef...@gmail.com
Subject: Re: NFS 75 second stall
To: alan bryanalan.br...@yahoo.com
Do you (or will you soon) have some patches I/we could test? I'm
willing to try anything to avoid mounting ten or so subdirectories in
each of my mount points.
Attached is a small patch for the only difference I can spot in the read
code between the regular and experimental NFS client.
I
- Original Message -
On Wed, Sep 01, 2010 at 11:46:30AM -0400, Rick Macklem wrote:
I am experiencing similar issues with newnfs:
1) I have two clients that each get around 0.5MiB/s to 2.6MiB/s
reading
from the NFS4-share on Gbit-Lan
2) Mounting with -t newnfs -o
On Wed, Sep 01, 2010 at 11:46:30AM -0400, Rick Macklem wrote:
I am experiencing similar issues with newnfs:
1) I have two clients that each get around 0.5MiB/s to 2.6MiB/s
reading
from the NFS4-share on Gbit-Lan
2) Mounting with -t newnfs -o nfsv3 results in no performance
1 - 100 of 367 matches
Mail list logo
