I set up NFSv4, did some performance tests, setup looks like this:
Server rc.conf:
nfs_server_enable="YES"
nfsv4_server_enable="YES"
nfsuserd_enable="YES"
exports:
/share -mapall=nobody 10.10.14.2 10.10.14.3
V4: / -sec=sys
Client(s) fstab mount:
srv:/share /m
Hi,
My system has been encountering kernel panic every time it accesses
large number of files over NFSv4.
The backtrace left after reboot (I haven't saved the core dump):
Dec 4 17:35:56 freebsd syslogd: kernel boot file is
/boot/kernel/kernel
Dec 4 17:35:56 freebsd kernel: panic:
hi,
i'm trying to mount some NFSv4 shares served by a Solaris 10 server on
our FreeBSD boxes. On FreeBSD 8.2, the mounts succeeded after
explicitly specifying the "resvport" mount option (the Solaris NFSd
refuses requests from unprivileged ports).
On 8.3, mount request
> >>> #!/bin/sh
> >>> # run this script where you wish to effect the changes
> >>> # reset perms to default
> >>> find . -type d -print0 | xargs -0 setfacl -b *
> >>
> >> Why the asterisk? Also, using "-m" with NFSv4 AC
). I'll look into it.
> >> However...
> >>
> >> [..]
> >>
> >>> #!/bin/sh
> >>> # run this script where you wish to effect the changes
> >>> # reset perms to default
> >>> find . -type d -print0 | xargs -0 setfac
this script where you wish to effect the changes
>>> # reset perms to default
>>> find . -type d -print0 | xargs -0 setfacl -b *
>>
>> Why the asterisk? Also, using "-m" with NFSv4 ACLs is not a very good
>> idea - it's supposed to work, but
t;
> -
>
> This itself looks like a bug in setfacl(1). I'll look into it.
> However...
>
> [..]
>
> > #!/bin/sh
> > # run this script where you wish to effect the changes
> > # reset perms to default
> > find . -type d -print0 | xargs -0 setf
ug in setfacl(1). I'll look into it. However...
[..]
> #!/bin/sh
> # run this script where you wish to effect the changes
> # reset perms to default
> find . -type d -print0 | xargs -0 setfacl -b *
Why the asterisk? Also, using "-m" with NFSv4 ACLs is not a very good
Hello all-
I've set up ZFS on a FreeBSD 9.0 64-bit server recently. One of the things I've
had to learn relates to NFSv4 ACLs. I've developed two scripts to reset
permissions- one for files and the other for folders. I've run into an issue
with executing a script to set pe
On Thu, Jan 12, 2012 at 05:37:57PM +0100, Leon Meßner wrote:
> Hi,
>
> Does anyone know what you have to do to get locking working under NFSv4?
> I tried the following:
>
> # mount_nfs -o nfsv4,sec=sys ip.nfsv4:/nfstest /mnt/test
> # mount | grep ip.nfsv4
> ip.nfsv4:/nfst
Hi,
Does anyone know what you have to do to get locking working under NFSv4?
I tried the following:
# mount_nfs -o nfsv4,sec=sys ip.nfsv4:/nfstest /mnt/test
# mount | grep ip.nfsv4
ip.nfsv4:/nfstest on /mnt/test (newnfs)
# kldstat | grep nfs
62 0x8103f000 1015fnfscommon.ko
91
I've run into a strange problem while trying to mount from FreeBSD
9.0-RC3 to anything I can find using NFSv4.
The command I'm using is:
#mount -v gorkon:/dustbin /tmp/test
This returns the following immediate information on a Debian 6 Linux box:
mount: no type was given - I
On 31/08/2011 23:45, David Brodbeck wrote:
I'm testing FreeBSD 9.0-BETA with an eye toward eventually using
FreeBSD 9.0 to replace some existing OpenSolaris 2008.11
installations. I've found NFS file creation performance (as measured
by Bonnie++) is equally slow for both with default settings.
I'm testing FreeBSD 9.0-BETA with an eye toward eventually using
FreeBSD 9.0 to replace some existing OpenSolaris 2008.11
installations. I've found NFS file creation performance (as measured
by Bonnie++) is equally slow for both with default settings. However,
on OpenSolaris I disable the ZIL to
On Tue, Aug 23, 2011 at 01:11:52AM +0200, Leon Meßner wrote:
> Hi,
>
> i'm just testing a kerberized NFSv4 export of a ZFS-Filesystem. Both
> client and server are FreeBSD at the moment. I tried Linux clients, but
> could not mount with sec=krb5. If i mount an exported dir
Hi,
i'm just testing a kerberized NFSv4 export of a ZFS-Filesystem. Both
client and server are FreeBSD at the moment. I tried Linux clients, but
could not mount with sec=krb5. If i mount an exported directory with
-o sec=krb5(i|p)i, directory listings with ls do sometimes take a very
long
teroperability testing between Linux and FreeBSD, I
>> came up with this unusual issue. I could use some help figuring out
>> if this is a bug, and if so, where to file it. Here's the scenario:
>>
>> - FreeBSD 8.1-RELEASE server, sharing a ZFS filesystem via NFSv4.
>
a ZFS filesystem via NFSv4.
I think that this is the beginning of your problems - even the developer
who is working on NFSv4 says it's too experimental to be used in real world.
- Linux client (I've tested with RHEL 5.4 and Debian Lenny) mounting
said filesystem with NFSv4.
- A us
While doing some interoperability testing between Linux and FreeBSD, I
came up with this unusual issue. I could use some help figuring out
if this is a bug, and if so, where to file it. Here's the scenario:
- FreeBSD 8.1-RELEASE server, sharing a ZFS filesystem via NFSv4.
- Linux client
On Tue, Aug 31, 2010 at 12:20 PM, David Brodbeck wrote:
> On Tue, Aug 31, 2010 at 11:52 AM, David Brodbeck wrote:
>> When a ZFS filesystem mountpoint is owned by someone other than root,
>> this is not depicted properly on NFSv4 clients:
>
> After playing around a bit
On Tue, Aug 31, 2010 at 11:52 AM, David Brodbeck wrote:
> When a ZFS filesystem mountpoint is owned by someone other than root,
> this is not depicted properly on NFSv4 clients:
After playing around a bit more, it appears the problem is that ZFS
filesystems under an NFSv4 mountpoint are no
When a ZFS filesystem mountpoint is owned by someone other than root,
this is not depicted properly on NFSv4 clients:
On the server (FreeBSD 8.1-RELEASE):
temp-nfs# zfs create tank/test/testfs
temp-nfs# chown brodbd:brodbd /tank/test/testfs
temp-nfs# touch /tank/test/testfile
temp-nfs# chown
Anybody?
Joe Auty wrote:
> Hello,
>
> I'm a little confused as to where NFSv4 is at... Is the client stable
> and considered ready for production use? If so, as of what OS version?
> The man page for nfsv4 listed here:
> http://www.freebsd.org/cgi/man.cgi?query=nfsv4&se
Hello,
I'm a little confused as to where NFSv4 is at... Is the client stable
and considered ready for production use? If so, as of what OS version?
The man page for nfsv4 listed here:
http://www.freebsd.org/cgi/man.cgi?query=nfsv4&sektion=4 still lists
this as experimental, however the
I managed to get NFSv4 working this weekend. Then I went to try to try
setting and ACL with setfacl and it wouldn't work. ACL's were the
reason I was interested in NFSv4. And I can't google the problem as I
keep getting pages refering to NFSv4 "style" ACL'
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
On 02/08/10 22:37, Rick Macklem wrote:
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&quo
On Mon, Feb 8, 2010 at 2:37 PM, Rick Macklem wrote:
> ps: ZFS also has its own export stuff, but it is my understanding that
>putting a line in /etc/exports is sufficient. I've never used ZFS,
>so others will know more than I.
>
My understanding (from having used NFS and ZFS, haven't loo
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/us
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
On 02/08/10 15:01, Rick Macklem wrote:
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
apps/daemons running locally on the server won't see byte range
locks performed by NFSv4 clients.) However, byte range locking between
NFSv4 clients should work ok.
rick
___
freebsd-sta...@freebsd.org mailing list
http://lists.freebsd.org/mailma
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
erver won't see byte range
locks performed by NFSv4 clients.) However, byte range locking between
NFSv4 clients should work ok.
rick
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubsc
Hello.
I set up a NFSv4 server located on a FreeBSD 8.0/amd64 box (most recent
world). It seems I successfully set up the NFSv4 service and this
results in a successful mount of a file system by another FreeBSD 8.0
box. But their is a weirdnes I do not understand.
Mounting the filessystem
I am running 8.0-RELEASE.
I am able to mount an nfsv4 share on a Debian GNU/Linux server, but I cannot
write to it. I realise that nfsv4 is experimental on FreeBSD, but I am
tantalisingly close to getting it working and thought that someone here could
advise, or point me to some (web
[dropping -current from CC]
O. Hartmann wrote:
> A simple capability of selecting users into a specific group. Members of
> such a group should then log into a set of specific hosts.
> Infrastructure is FreeBSD 8.0-CURRENT/amd64 and some 7.2-STABLE boxes
> (acting as server) as well as OpenLDAP
O. Hartmann schrieb am 27.04.2009 09:48 (localtime):
...
This is what I wish to get and need:
A simple capability of selecting users into a specific group. Members of
such a group should then log into a set of specific hosts.
Infrastructure is FreeBSD 8.0-CURRENT/amd64 and some 7.2-STABLE boxes
Hello.
I run into a specific problem and for several months of experiments I
havn't found a solution, yet.
This is what I wish to get and need:
A simple capability of selecting users into a specific group. Members of
such a group should then log into a set of specific hosts.
Infrastructure is
Konrad Heuer wrote:
> are there any experiences with FreeBSD being an NFSv4 client out there?
>
> And furthermore, is there any further development of NFSv4 functionality
> within FreeBSD to come closer to RFC 3530?
As far as I know (not 100% sure, though), the NFSv4 client
is
Hello everyone,
are there any experiences with FreeBSD being an NFSv4 client out there?
And furthermore, is there any further development of NFSv4 functionality
within FreeBSD to come closer to RFC 3530?
Thanks for any reply and best regards
Konrad Heuer
GWDG, Am Fassberg, 37077 Goettingen
Hi
we have a Solaris 10 NFS server and a FreebSD 7.0 NFS client.
We have a couple of NFSv4 mounted filesystem on the client.
nest.ifom-ieo-campus.it:/data/exports/obj/bsd7.ifom-ieo-campus.it/obj
/mnt/nest nfs rw,-r=16384,-w=16384,tcp,-4 2 0
nest.ifom-ieo-campus.it:/data
Hi all!
I've been running my home file server on Linux for quite a number of
years, but ever since I started running FreeBSD on my laptop, I've
been itching a bit to start looking into reinstalling the file server
with FreeBSD as well. There's just one show-stopper: There seems not
to be any Kerbe
On Tue, Feb 28, 2006 at 02:13:12AM +0100, Albert Shih wrote:
> Hi all
>
> Any idea when the a nfsv4 server working on FreeBSD ?
See the freebsd-fs archives.
Kris
pgpqr6sH6FTZI.pgp
Description: PGP signature
Hi all
Any idea when the a nfsv4 server working on FreeBSD ?
Regards.
--
Albert SHIH
Universite de Paris 7 (Denis DIDEROT)
U.F.R. de Mathematiques.
7 ième étage, plateau D, bureau 10
Heure local/Local time:
Tue Feb 28 02:12:16 CET 2006
___
freebsd
Hi all.
Anyone known the quality of mount_nfs4 ? And where can I find a nfsv4
server ? Of course I prefer on my FreeBSD box ;-))
Regards.
--
Albert SHIH
Universite de Paris 7 (Denis DIDEROT)
U.F.R. de Mathematiques.
Heure local/Local time:
Mon Jan 16 22:42:07 CET 2006
ed
Boot interrupted
Enter full pathname of shell or RETURN for /bin/sh:
..
This is due to the fact that the system is trying to mount the NFSv4
filesystem before the network stack is up (as per /etc/rc.d/mountcritlocal).
If NFSv4 is stable code under the 5.3-tree, then it may be wise to add
I ran into this problem while mounting a netapp with nfsv4 during a reboot.
Should /etc/defaults/rc.conf have "nfs4" in the "netfs_types" list? I know I
can add it to the "extra_netfs_types" variable under /etc/rc.conf, but if
it's stable code, then it might
48 matches
Mail list logo
