patch to add a Linux compatible copy_file_range(2) syscall

2019-06-09 Thread Rick Macklem
Hi, I just put a patch in phabricator that is intended to add a Linux compatible copy_file_range(2) syscall. My main interest in having this is that NFSv4.2 will know how to do file copying locally on the NFS server, saving all the reads/writes across the wire. It copies the file byte range in

Re: adding a syscall to libc?

2019-06-09 Thread Rick Macklem
Konstantin Belousov wrote: >On Sat, Jun 08, 2019 at 02:57:27AM +0000, Rick Macklem wrote: >> Hi, >> First off, thanks Kostik for the fine explanation. I agree with Oliver that it should be captured somewhere like the wiki. I'm no wiki guy, so hopefully someone else will do this?

adding a syscall to libc?

2019-06-07 Thread Rick Macklem
Hi, I've started working of a copy_file_range() syscall for FreeBSD. I think I have the kernel patched and ready for some testing. However, I'm confused about what I need to do in src/lib/libc/sys? - Some syscalls have little .c files, but other ones do not. When is one of these little .c

Re: RFC w.r.t. toggling debugging on/off for mountd via a signal

2019-05-19 Thread Rick Macklem
Cy Schubert wrote: [lots of stuff snipped] >Instead of syslog() calls, DTrace probes are designed for this type of >instrumentation. DTrace us way too obscure for me. Never used it, probably never will. (Remember I'm the guy who still uses "ed" to edit

Re: RFC w.r.t. toggling debugging on/off for mountd via a signal

2019-05-18 Thread Rick Macklem
Alan Somers wrote: >On Sat, May 18, 2019 at 7:59 PM Rick Macklem wrote: >> >> Hi, >> >> I've been working with Peter Errikson on a patch for mountd that adds a new >> option >> for incremental updating of exports. This seems to be helping a lot w.r

RFC w.r.t. toggling debugging on/off for mountd via a signal

2019-05-18 Thread Rick Macklem
Hi, I've been working with Peter Errikson on a patch for mountd that adds a new option for incremental updating of exports. This seems to be helping a lot w.r.t. performance on an NFS server with lots (1+) of exported file systems. I have debug syslog() calls in the code, which I/Peter

patch that replaces a single linked list with a hash table of lists (mountd.c) for review

2019-05-15 Thread Rick Macklem
Hi, I just put a patch for mountd.c in phabricator as D20270, which replaces the single linked list of structures for exported file systems with a hash table of lists. This is part of what I hope will fix the performance of mountd when reloading the exports file(s) for a server with a lot of

Re: Do the pidhashtbl_locks added by r340742 need to be sx locks?

2019-04-10 Thread Rick Macklem
Mateusz Guzik wrote: >On 4/11/19, Rick Macklem wrote: >> Hi, >> >> I finally got around to looking at what effect replacing pfind_locked() >> with >> pfind() has for the NFSv4 client and it is broken. >> >> The problem is that the NFS code nee

Do the pidhashtbl_locks added by r340742 need to be sx locks?

2019-04-10 Thread Rick Macklem
Hi, I finally got around to looking at what effect replacing pfind_locked() with pfind() has for the NFSv4 client and it is broken. The problem is that the NFS code needs to call some variant of "pfind()" while holding a mutex lock. The current _pfind() code uses the pidhashtbl_locks, which are

Re: what do jails map 127.0.0.1 to?

2019-02-16 Thread Rick Macklem
Rodney W. Grimes wrote: [stuff snipped] > ipv4 127.0.0.1 == ipv6 ::1, see /etc/hosts Thanks. I've created D19218 with the patch for nfsuserd.c to both check the mapping of localhost and adding support for IPv6. I've listed bz@ as a reviewer, but if anyone else would like to review it, feel to do

Re: what do jails map 127.0.0.1 to?

2019-02-12 Thread Rick Macklem
Bjoern A. Zeeb wrote: [good stuff snipped] >Yes, could do easily but wouldn’t work for my above case, would it? I >can help you with the code for v4 and jails if you help me with the code >for IPv6? Well, not quite what you volunteered to do, but can you fill in the INET6 code for this code

Re: what do jails map 127.0.0.1 to?

2019-02-12 Thread Rick Macklem
Bjoern A. Zeeb wrote: >On 11 Feb 2019, at 0:50, Rick Macklem wrote: >> I am finally back to looking at an old PR#205193. >> >> The problem is that the nfsuserd daemon expects upcalls from the >> kernel >> that are from localhost (127.0.0.1) and when jails are runni

what do jails map 127.0.0.1 to?

2019-02-10 Thread Rick Macklem
I am finally back to looking at an old PR#205193. The problem is that the nfsuserd daemon expects upcalls from the kernel that are from localhost (127.0.0.1) and when jails are running on the system, 127.0.0.1 is mapped to some other IP#. (I think it might be the address of the first net

possible POLA violation for NFS server to make it Linux compatible

2018-12-18 Thread Rick Macklem
It was my understanding that the NFSv4 working group believed that the requirement for the NFSv4 client to use a priviledged port# (< 1024) should not exist. As such, I coded the server to ignore the vfs.nfsd.nfs_privport sysctl and allow the mount for NFSv4. PR#234106 has reported this as a

Re: which way to update export_args structure?

2018-10-22 Thread Rick Macklem
From: owner-freebsd-curr...@freebsd.org on behalf of Rick Macklem Sent: Monday, October 22, 2018 5:24 PM To: Brooks Davis Cc: FreeBSD Current; Josh Paetzel Subject: Re: which way to update export_args structure? Brooks Davis wrote: On Sat, Oct 20

Re: which way to update export_args structure?

2018-10-22 Thread Rick Macklem
Brooks Davis wrote: On Sat, Oct 20, 2018 at 01:17:37AM +, Rick Macklem wrote: [lots of stuff snipped] >> + if (error == 0) { >> + gotexp = 0; >> + memset(, 0, sizeof(export)); >> + if (vfs_getopt(mp->

Re: which way to update export_args structure?

2018-10-19 Thread Rick Macklem
Brooks Davis wrote: > Yes, I think that's the right way foward. Thanks for following up. >Rick Macklem wrote: >> Just in case you missed it in the email thread, in your general question >> below... >> Did you mean/suggest that the fields of "struct export_args

Re: which way to update export_args structure?

2018-10-03 Thread Rick Macklem
Brooks Davis wrote: >On Wed, Oct 03, 2018 at 12:40:27AM +0000, Rick Macklem wrote: >> Hi, >> >> I am working on updating "struct export_args" to fix/add a few things. >> One of these is that "ex_flags" is an int, but the flags are defined in >

Re: which way to update export_args structure?

2018-10-03 Thread Rick Macklem
Gary Jennejohn wrote: [stuff snipped] >In B, shouldn't ex_flags become uint32_t if all 32 bits can contain >flag bits? You could. For B) my intent was to leave the structure exactly the same as the old versions and only add new fields at the end. The current compatibility code in head does

Re: which way to update export_args structure?

2018-10-02 Thread Rick Macklem
I wrote: >Hi, > >I am working on updating "struct export_args" to fix/add a few things. >One of these is that "ex_flags" is an int, but the flags are defined in mount.h >as MNT_xx bits that now exceed 32bits (mnt_flag is now uint64_t). >For now, this doesn't break anything, since the flags used by

which way to update export_args structure?

2018-10-02 Thread Rick Macklem
Hi, I am working on updating "struct export_args" to fix/add a few things. One of these is that "ex_flags" is an int, but the flags are defined in mount.h as MNT_xx bits that now exceed 32bits (mnt_flag is now uint64_t). For now, this doesn't break anything, since the flags used by ex_flags are

Heads up: nfsuserd -use-udpsock option no longer used

2018-08-22 Thread Rick Macklem
As of r338192 the command line option "-use-udpsock" no longer exists, since r320757 has been reverted. The behaviour is now back to always using a UDP socket the same as stable/11. In other words, if you are using the nfsuserd with the "-use-udpsock" option, just get rid of the "-use-udpsock"

Re: panic excl->shared for an AF_LOCAL socket

2018-08-21 Thread Rick Macklem
Matthew Macy wrote: [stuff snipped] >I don't know what's special in this case, but I did revamp the locking there >several >months back so I'll take a look next weekend. Thanks but don't worry about it for now. I think I figured out how the panic() occurred. If the nfsd was accessing

panic excl->shared for an AF_LOCAL socket

2018-08-19 Thread Rick Macklem
Hi, PR#230752 shows a witness panic() for "excl->shared" on a vnode lock. In this case, the kernel RPC code is trying to do a soconnect() on an AF_LOCAL socket. The code is unp_connectat() looks like is does a straightforward namei()/lookup(), so I am surprised to see this. Does anyone know if

Re: ffs_truncate3 panics

2018-08-17 Thread Rick Macklem
Just fyi, I have committed r337962 to head, which stops the pNFS service from creating non-zero length empty files. Since these files were the ones causing the "ffs_truncate3" panics, the panics should no longer occur. I will take a closer look at some point to see if I can spot why the panics()

Re: kernel build failure

2018-08-13 Thread Rick Macklem
Rodney W. Grimes wrote: >> On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: >> >> > Sorry guys, last time I touched ZFS I tried to push to make it an option to >> > statically link and was actually told that it wasn't something anyone else >> > wanted. The issue comes from ZFS not being in

Re: ffs_truncate3 panics

2018-08-12 Thread Rick Macklem
Konstantin Belousov wrote: [stuff snipped] >Problem with this buffer is that BX_ALTDATA bit is not set. >This is the reason why vinvalbuf(V_ALT) skips it. [more stuff snipped] >The vnode is exclusively locked. Other thread must not be able to >instantiate a buffer under us. That's what I thought,

Re: ffs_truncate3 panics

2018-08-11 Thread Rick Macklem
Konstantin Belousov wrote: >On Thu, Aug 09, 2018 at 08:38:50PM +0000, Rick Macklem wrote: >> >BTW, does NFS server use extended attributes ? What for ? Can you, please, >> >point out the code which does this ? >> For the pNFS service, there are two system na

Re: ffs_truncate3 panics

2018-08-10 Thread Rick Macklem
Konstantin Belousov wrote: >On Thu, Aug 09, 2018 at 08:38:50PM +0000, Rick Macklem wrote: >> I did notice that my code locks the vnode first and then calls >> vn_start_write() >> for the vn_extattr_set() calls, whereas the syscall code locks the vnode >> afte

Re: ffs_truncate3 panics

2018-08-09 Thread Rick Macklem
Konstantin Belousov wrote: [stuff snipped] >I wrote: >> >> I can add printf()s anywhere you suggest, but I'm not sure how you would >> catch >> this case sooner? (For example, I could print out di_extsize at the >> beginning of >> ffs_truncate(), if that would help?) >May be, add a loop at the

Re: ffs_truncate3 panics

2018-08-09 Thread Rick Macklem
Rodney W. Grimes wrote: [stuff snipped] >It should be possible to design a set of VM's using bhyve, xen or ones >favorite hypervisor/virtulization platform to do "more" pNFS testing. >If you could provide a rought machine set needed to have a functional >test bed, and what should be done to "test"

Re: ffs_truncate3 panics

2018-08-08 Thread Rick Macklem
Konstantin Belousov wrote: [stuff snipped] >> >Can you print the only buffer on the clean queue when the panic occur ? >> ffst3 vtyp=1 bodirty=0 boclean=1 >> buf at 0x428a110 >> b_flags = 0x20001020, b_xflags=0x2, b_vflags=0x0 >> b_error = 0, b_bufsize = 4096, b_bcount = 4096, b_resid = 0 >>

Re: ffs_truncate3 panics

2018-08-08 Thread Rick Macklem
Konstantin Belousov wrote: >On Tue, Aug 07, 2018 at 12:28:33PM +0000, Rick Macklem wrote: >> Hi, >> >> During testing of the pNFS server I get an ffs_truncate3 panic every once in >> a while. >> A few things that might be relevant: >> - Seems to happen

ffs_truncate3 panics

2018-08-07 Thread Rick Macklem
Hi, During testing of the pNFS server I get an ffs_truncate3 panic every once in a while. A few things that might be relevant: - Seems to happen more often when soft update journaling is enabled, but will happen when it is disabled. - Normally happens when a fairly large subtree of the file

Re: NFSv4.1 server deficiencies fixed for ESXi client

2018-07-15 Thread Rick Macklem
I wrote: > (I am going to look and see what the Linux server does for this case.) I just looked and the Linux 4.17-rc2 kernel NFS server just returns NFS_OK for the rca_one_fs == TRUE case. I have given a patch that does the same thing for the FreeBSD server to Andreas and Daniel and think it is

Re: NFSv4.1 server deficiencies fixed for ESXi client

2018-07-15 Thread Rick Macklem
Rodney W. Grimes wrote: >Have you any contact with VMWare so that they might fix the issues >in thier code, rather than having to put hacks in FreeBSD for these >issues? Well, Jim White (who is not in their file system area) submitted a PR on their system and the response was along the lines of:

Heads Up: rebuild nfsd if using the "-p" option

2018-07-02 Thread Rick Macklem
r335870 changes the interface between the nfsd and the kernel for the case where the "-p" option is used, so if you are using "nfsd -p" you should rebuild your nfsd from sources of r335871 or later. To be honest, I didn't see problems during testing, but I think that is because there are some

change of nfsd->kernel interface in head

2018-06-30 Thread Rick Macklem
r335012 (the big patch that added the pNFS server support) revised the nfsd->kernel nfssvc(2) syscall interface. It has compatibility code, so that old nfsd binaries still work. I now need to revise this interface again to add a new pNFS server feature. Since the revised interface is only in

Re: nfsd kernel threads won't die via SIGKILL

2018-06-26 Thread Rick Macklem
Konstantin Belousov wrote: On Mon, Jun 25, 2018 at 02:04:32AM +, Rick Macklem wrote: > Konstantin Belousov wrote: > >On Sat, Jun 23, 2018 at 09:03:02PM +0000, Rick Macklem wrote: > >> During testing of the pNFS server I have been frequently > >> killing/res

Re: nfsd kernel threads won't die via SIGKILL

2018-06-24 Thread Rick Macklem
Konstantin Belousov wrote: >On Sat, Jun 23, 2018 at 09:03:02PM +0000, Rick Macklem wrote: >> During testing of the pNFS server I have been frequently killing/restarting >> the nfsd. >> Once in a while, the "slave" nfsd process doesn't terminate and a "ps axH

nfsd kernel threads won't die via SIGKILL

2018-06-23 Thread Rick Macklem
During testing of the pNFS server I have been frequently killing/restarting the nfsd. Once in a while, the "slave" nfsd process doesn't terminate and a "ps axHl" shows: 0 48889 1 0 20 0 5884 812 svcexit D - 0:00.01 nfsd: server 0 48889 1 0 40 0 5884 812 rpcsvc

Re: head -r335568 breaks the ci.freebsd.org builds of the various FreeBSD-head-*-build

2018-06-22 Thread Rick Macklem
Mark Millard wrote: >from the likes of: > >https://ci.freebsd.org/job/FreeBSD-head-sparc64-build/8346/consoleText > >--- nfs_commonkrpc.o --- >/usr/src/sys/fs/nfs/nfs_commonkrpc.c: In function 'newnfs_request': >/usr/src/sys/fs/nfs/nfs_commonkrpc.c:813: error: 'ND_HASSLOTID' undeclared >(first

Re: ESXi NFSv4.1 client id is nasty

2018-06-19 Thread Rick Macklem
Steve Wills wrote: On 06/18/18 17:42, Rick Macklem wrote: >> Steve Wills wrote: >>> Would it be possible or reasonable to use the client ID to log a message >>> telling the admin to enable a sysctl to enable the hacks? >> Yes. However, this client implementation

Re: review of nfsd rc.d script patch

2018-06-19 Thread Rick Macklem
Don Lewis wrote: >On 15 Jun, Rick Macklem wrote: >> Hi, >> >> For the pNFS service MDS machine, the nfsd can't be started until all nfs >> mounts >> in /etc/fstab are done. >> I think that adding "mountcritremote" to the "# REQUIRE:" line

Re: ESXi NFSv4.1 client id is nasty

2018-06-18 Thread Rick Macklem
essage and fail the mount, if the "hack" sysctl isn't set? rick [stuff snipped] From: Steve Wills Sent: Monday, June 18, 2018 5:21:10 PM To: Rick Macklem; freebsd-current@freebsd.org Cc: andreas.n...@frequentis.com Subject: Re: ESXi NFSv4.1 cl

RFC: ESXi client is nasty, what should I do?

2018-06-18 Thread Rick Macklem
Hi, I realized that the subject line "ESXi NFSv4.1 client id is nasty" wouldn't have indicated that I was looking for comments w.r.t. how to handle this poorly behaved client. Please go to the "ESXi NFSv4.1 client id is nasty" thread and comment. (It should be in the archive, if you already

Re: NFSv4.1 server deficiencies fixed for ESXi client

2018-06-17 Thread Rick Macklem
Rodney W. Grimes wrote: [stuff snipped] >Have you any contact with VMWare so that they might fix the issues >in their code, rather than having to put hacks in FreeBSD for these >issues? Nope. I tried an email to nf...@ietf.org about one issue (that isn't yet resolved related to it complaining

NFSv4.1 server deficiencies fixed for ESXi client

2018-06-17 Thread Rick Macklem
Hi, Since I posted w.r.t. issues that seem to violate the RFC, I figured I should also post ones that identified deficiencies in the FreeBSD server. These have either been patched in head/current or will be soon and will be MFC'd. - BindConnectiontoSession wasn't implemented. It is never used

ESXi NFSv4.1 client id is nasty

2018-06-17 Thread Rick Macklem
Hi, Andreas Nagy has been doing a lot of testing of the NFSv4.1 client in ESXi 6.5u1 (VMware) against the FreeBSD server. I have given him a bunch of hackish patches to try and some of them do help. However not all issues are resolved. The problem is that these hacks pretty obviously violate the

review of nfsd rc.d script patch

2018-06-15 Thread Rick Macklem
Hi, For the pNFS service MDS machine, the nfsd can't be started until all nfs mounts in /etc/fstab are done. I think that adding "mountcritremote" to the "# REQUIRE:" line is sufficient to do this? I don't think delaying the startup of the nfsd daemon until after any NFS mounts are done will do

Re: utilities in /usr/bin or /usr/sbin?

2018-06-14 Thread Rick Macklem
Rodney W. Grimes wrote: ?> On Thu, Jun 14, 2018 at 2:15 PM, Rick Macklem wrote: >> >> > Hi, >> > >> > I have three new utilities that are mainly useful for managing the pNFS >> > server >> > committed as r335130. >> > >> >

Re: utilities in /usr/bin or /usr/sbin?

2018-06-14 Thread Rick Macklem
I wrote: >I have three new utilities that are mainly useful for managing the pNFS server >committed as r335130. Oops, I meant r334930, although it doesn't really affect the question. >In the projects tree, I have them in /usr/bin and man section 1. However, >since they are mostly useful to a

utilities in /usr/bin or /usr/sbin?

2018-06-14 Thread Rick Macklem
Hi, I have three new utilities that are mainly useful for managing the pNFS server committed as r335130. In the projects tree, I have them in /usr/bin and man section 1. However, since they are mostly useful to a sysadmin managing the pNFS service, I'm thinking that maybe they should be in

Heads Up: pNFS server merge committed to head

2018-06-12 Thread Rick Macklem
Since I only got one response to my query w.r.t. should projects/pnfs-planb-server be merged into head and it wasn't negative, I went with "no news is good news" and did the merge/commit. It is now in head as r335012. Since it has survived a recent "make universe", I hope it won't cause build

Re: how do I use the make universe machines?

2018-06-07 Thread Rick Macklem
Just replying to one of the messages at random... Benjamin Kaduk wrote: [stuff snipped] >I think https://www.freebsd.org/internal/machines.html sounds like >the page you're looking for. (universe is just a top-level make >target like buildworld, but will take a while on non-beefy >hardware.) Yea,

how do I use the make universe machines?

2018-06-05 Thread Rick Macklem
I've heard mention of "make universe" machines multiple times, but have no idea how to use them? Is there doc on this? Thanks, rick ps: I'll admit I haven't looked at the developer's guide in a long time. ___ freebsd-current@freebsd.org mailing list

Re: how to deal with variable set but not used warnings?

2018-06-04 Thread Rick Macklem
Matthew Macy wrote: >On Sun, Jun 3, 2018 at 2:40 PM, Theron wrote: >>> 4. Disable the stupid warning in the Makefile / build system. If you don't >>> care, and there's a good reason for what you are doing (sounds like there >>> is), better to just disable the warning as so much useless noise. >>>

how to deal with variable set but not used warnings?

2018-06-03 Thread Rick Macklem
mmacy has sent me a bunch of warnings of the "variable set but not used" kind generated by gcc8. When I've looked at the code, these are for RPC arguments I parse but do not use at this time. I'd like to leave the code in place, since these arguments may be needed in the future and it is hard to

SPDX-License-Id for new files

2018-06-03 Thread Rick Macklem
I have a few (3) new files in the projects/pnfs-planb-server subversion tree that all have the 2 clause FreeBSD copyright. Do I just add the "SPDX..." line for this license at the top of the copyright comment or is there some other exercise needed to be done for this? Thanks, rick

Re: mlx5(4) jumbo receive

2018-04-25 Thread Rick Macklem
Ryan Stone wrote: >On Tue, Apr 24, 2018 at 4:55 AM, Konstantin Belousov >>>wrote: >> +#ifndef MLX5E_MAX_RX_BYTES >> +#defineMLX5E_MAX_RX_BYTES MCLBYTES >> +#endif > >Why do you use a 2KB buffer rather than a PAGE_SIZE'd buffer? >MJUMPAGESIZE should offer significantly

Re: SCHED_ULE makes 256Mbyte i386 unusable

2018-04-22 Thread Rick Macklem
Konstantin Belousov wrote: >On Sat, Apr 21, 2018 at 11:30:55PM +0000, Rick Macklem wrote: >> Konstantin Belousov wrote: >> >On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: >> >> I decided to start a new thread on current related to SCHED_ULE, since I

Re: i386 hangs during halt "vnodes remaining... 0 time out"

2018-04-22 Thread Rick Macklem
Konstantin Belousov wrote: >On Sat, Apr 21, 2018 at 11:49:34PM +0200, Tijl Coosemans wrote: >> On Sat, 21 Apr 2018 21:09:09 +0000 Rick Macklem <rmack...@uoguelph.ca> wrote: >> > With a recent head/current kernel (doesn't happen when running a Dec. >> > 2017 one),

Re: i386 hangs during halt "vnodes remaining... 0 time out"

2018-04-21 Thread Rick Macklem
ent-Type: text/plain; charset=US-ASCII >> > Content-Transfer-Encoding: 7bit >> > Content-Disposition: inline >> > >> > On Sat, 21 Apr 2018 21:09:09 + Rick Macklem <rmack...@uoguelph.ca> wrot >> e: >> > > With a recent head/current kernel

Re: SCHED_ULE makes 256Mbyte i386 unusable

2018-04-21 Thread Rick Macklem
Konstantin Belousov wrote: >On Sat, Apr 21, 2018 at 07:21:58PM +0000, Rick Macklem wrote: >> I decided to start a new thread on current related to SCHED_ULE, since I see >> more than just performance degradation and on a recent current kernel. >> (I cc'd a couple of

i386 hangs during halt "vnodes remaining... 0 time out"

2018-04-21 Thread Rick Macklem
With a recent head/current kernel (doesn't happen when running a Dec. 2017 one), when I do a halt, it gets as far as: vnodes remaining... 0 time out and that's it (the time out appears several seconds after the first "0"). With a Dec. 2017 kernel there would be several "0"s printed. It appears

SCHED_ULE makes 256Mbyte i386 unusable

2018-04-21 Thread Rick Macklem
I decided to start a new thread on current related to SCHED_ULE, since I see more than just performance degradation and on a recent current kernel. (I cc'd a couple of the people discussing performance problems in freebsd-stable recently under a subject line of "Re: kern.sched.quantum: Creepy,

Re: anyone running with ngroups increased from 16?

2018-04-16 Thread Rick Macklem
Brooks Davis wrote: >On Mon, Apr 16, 2018 at 06:37:53PM +0800, Julian Elischer wrote: >> Windows users seem to have an almost unlimited number of groups and=20 >> soem places seem to use them a LOT. >> This gives Posix systems problems with deciding how to handle them=20 >> all. Especially when

Re: anyone running with ngroups increased from 16?

2018-04-16 Thread Rick Macklem
Julian Elischer wrote: >On 16/4/18 6:37 pm, Julian Elischer wrote: >> Windows users seem to have an almost unlimited number of groups and >> soem places seem to use them a LOT. >> This gives Posix systems problems with deciding how to handle them >> all. Especially when getting >> user credentials

Re: NFSv4.2

2017-12-11 Thread Rick Macklem
Stefan Wendler wrote: > We would like to use the file copy and the sparse features of 4.2 in our > Setup. Do you know if any of the two has been implemented yet? The > sparse feature would be more important than the file copy feature though. No idea (except that NFSv4.2 isn't in FreeBSD which

Re: NFSv4.2

2017-12-11 Thread Rick Macklem
Stefan Wendler wrote: > I was wondering when and if FreeBSD will support NFSv4.2 > Is there anything planned yet? Someday, but no specific plans at this point. Is there some specific feature in NFSv4.2 that you are looking for? I ask because there isn't a lot of new features in NFSv4.2 that

Re: Switch vfs.nfsd.issue_delegations to TUNABLE ?

2017-12-01 Thread Rick Macklem
urr...@freebsd.org> on behalf of Rick Macklem <rmack...@uoguelph.ca> Sent: Wednesday, November 29, 2017 12:28:05 PM To: Emmanuel Vadot Cc: Konstantin Belousov; FreeBSD Current; freebsd...@freebsd.org Subject: Re: Switch vfs.nfsd.issue_delegations to TUNABLE ? Emmanuel Vadot wrote: [stuff

Re: Switch vfs.nfsd.issue_delegations to TUNABLE ?

2017-11-29 Thread Rick Macklem
Emmanuel Vadot wrote: [stuff snipped] > I haven't test by I can say that it will work, I actually wondered at >first doing that. The problem with this patch is what I tried to >describe in my first and following mails, since you can turn on and off >delegation you can still have delegation (so

Re: Switch vfs.nfsd.issue_delegations to TUNABLE ?

2017-11-28 Thread Rick Macklem
Did my usual and forgot to attach it. Here's the patch, rick From: Rick Macklem <rmack...@uoguelph.ca> Sent: Tuesday, November 28, 2017 6:17:13 PM To: Emmanuel Vadot Cc: Konstantin Belousov; FreeBSD Current; freebsd...@freebsd.org; Rick Macklem Subje

Re: Switch vfs.nfsd.issue_delegations to TUNABLE ?

2017-11-28 Thread Rick Macklem
and use atomics to increment/decrement it so that it is SMP safe without acquiring any lock. If you can test this, please let me know how it goes? rick From: Rick Macklem <rmack...@uoguelph.ca> Sent: Tuesday, November 28, 2017 2:09:51 PM To: Emmanuel Va

Re: Switch vfs.nfsd.issue_delegations to TUNABLE ?

2017-11-28 Thread Rick Macklem
Emmanuel Vadot wrote: >I wrote: >> Since it defaults to "disabled", I don't see why a tunable would be >> necessary? >> (Just do nothing and delegations don't happen. If you want the server >> to issue delegations, then use the sysctl to turn them on. If you want to >> turn >> them off again

Re: Switch vfs.nfsd.issue_delegations to TUNABLE ?

2017-11-28 Thread Rick Macklem
Konstantin Belousov wrote: >On Tue, Nov 28, 2017 at 02:26:10PM +0100, Emmanuel Vadot wrote: >> On Tue, 28 Nov 2017 13:04:28 +0200 >> Konstantin Belousov wrote: >> >> > On Tue, Nov 28, 2017 at 11:41:36AM +0100, Emmanuel Vadot wrote: >> > > >> > > Hello, >> > > >> > > I would

pNFS server code merge into head/current

2017-11-25 Thread Rick Macklem
Hi, There is a source tree in svn at projects/pnfs-planb-server which adds support for configuring a single Metadata Server (MDS) and multiple Data Servers (DS) to create a simple pNFS service. (In a pNFS server the Read/Write operations are separated from the rest of the metadata operations and

Re: Mergemaster won't run on NFS mount

2017-11-23 Thread Rick Macklem
Thomas Laus wrote: >My /etc/exports file is empty. I have set the sharenfs property to >'YES" on the /usr/obj and /usr/src data sets. The ZFS filesystem >handles NFS shares internally from the documenation. It still reloads the exports, so the outcome is the same. >In any event, >this is how my

Re: Mergemaster won't run on NFS mount

2017-11-22 Thread Rick Macklem
Thomas Laus wrote: >I have been updating FreeBSD for years on my fastest computer and then >NFS mounting /usr/src and /usr/obj to share with other PC's. I just >updated FreeBSD-CURRENT to 326070 and was able to install the kernel and >world. When I attempted to run mergemaster, I received the

Re: NFSv3 issues with latest -current

2017-10-31 Thread Rick Macklem
Rodney W. Grimes wrote: [stuff snipped] > I wrote: >> Btw, NFS often causes this because... >> - Typically TSO is limited to a 64K packet (including TCP/IP and MAC >> headers). >> - When NFS does reading/writing, it will do 64K + NFS, TCP/IP and MAC headers >> for an RPC (or a multiple of 64K

Re: NFSv3 issues with latest -current

2017-10-31 Thread Rick Macklem
Cy Schubert wrote: [stuff snipped] >The sysctl is net.inet.tcp.tso. You can also disable tso through ifconfig >for an interface. > For testing this case, I'd recommend using the sysctl. Since the net device driver is often the culprit, that device driver might not handle the "ifconfig" correctly

Re: NFSv3 issues with latest -current

2017-10-29 Thread Rick Macklem
Yuri Pankov wrote: > All file operations (e.g. copying the file over NFSv3 for me) seem to be > stuck running the latest -current (r325100). Reverting just the kernel > to r323779 (arbitrary chosen) seems to help. I noticed the "Stale file > handle when mounting nfs" message but I don't get the

Re: pfind_locked(pid) fails when in a jail?

2017-10-17 Thread Rick Macklem
Mateusz Guzik wrote: [lots of stuff snipped] > I proposed registration of per-process callbacks, not filtering. > The code would just walk the list/table/whatever and call everything on > it - they asked for it. Yep, this would work for the NFSv4 client. Way back when, all I did in OpenBSD was add

Re: pfind_locked(pid) fails when in a jail?

2017-10-16 Thread Rick Macklem
[stuff snipped] > > > > > pfind* does not do any filtering. > > Hmm, well I have no idea why the jailed mounts get looping in here then. > > The real question though is why are you calling it in the first place. The > > calls > > I grepped in nfscl_procdoesntexist are highly suspicious - there is

pfind_locked(pid) fails when in a jail?

2017-10-16 Thread Rick Macklem
Hi, A problem w.r.t. the NFSv4 client's renew thread (nfscl) running up a lot of CPU when the NFSv4 mount is in a jail has been reported to the freebsd-stable@ mailing list. I know nothing about jails, but when looking at the code, the most obvious cause of this would be "pfind_locked(pid)"

Re: RFC how to use kernel procs/threads efficiently

2017-10-10 Thread Rick Macklem
Julian Elischer wrote: [stuff snipped] >On 10/10/17 4:25 am, Rick Macklem wrote: >> --> As such, having a fixed reasonable # of threads is probably the best >>that can be done. >>- The current patch has the # of threads as a sysctl with a default >>

Re: RFC how to use kernel procs/threads efficiently

2017-10-09 Thread Rick Macklem
Ian Lepore wrote: [stuff snipped] >taskqueue(9) is an existing mechanism to enqueue functions to execute >asynch using a pool of threads, but it doesn't answer the scalability >questions. In fact it may make them harder, inasmuch as I don't think >there's

Re: RFC how to use kernel procs/threads efficiently

2017-10-07 Thread Rick Macklem
Ian Lepore wrote: >On Fri, 2017-10-06 at 19:02 +0000, Rick Macklem wrote: >> Hi, >> >> I have now dropped the client side of Flexible File Layout for pNFS into head >> and I believe it is basically working. >> Currently when talking to mirrored DS servers, it

RFC how to use kernel procs/threads efficiently

2017-10-06 Thread Rick Macklem
Hi, I have now dropped the client side of Flexible File Layout for pNFS into head and I believe it is basically working. Currently when talking to mirrored DS servers, it does the Write and Commit RPCs to the mirrors serially. This works, but is inefficient w.r.t. elapsed to to completion. To

Re: panic in AcpiOsGetTimer during boot.

2017-10-02 Thread Rick Macklem
36 kernel. If it still panics, I'll post again. Thanks, rick > Best, > Conrad On Sun, Oct 1, 2017 at 3:12 PM, Rick Macklem <rmack...@uoguelph.ca> wrote: > Hi, > > I get the KASSERT panic in AcpiOsGetTimer() while booting a recent (2 day old) > kernel. When I delete the KASS

panic in AcpiOsGetTimer during boot.

2017-10-01 Thread Rick Macklem
Hi, I get the KASSERT panic in AcpiOsGetTimer() while booting a recent (2 day old) kernel. When I delete the KASSERT(), the kernel boots and seems to work ok. (This is the AcpiOsGetTimer() in sys/dev/acpica/Osd/OsdSchedule.c. There also seems to be one of these functions under contrib.) Here is

Re: Can't NFS mount ZFS volume

2017-10-01 Thread Rick Macklem
Danny Braniss wrote: > Michael Butler wrote: >> I have no idea why but using .. >> >> sudo /sbin/mount vm01:/usr/local/exports/ /mnt >> .. instead of .. >> >> sudo /sbin/mount -t nfs vm01:/usr/local/exports/ /mnt > > the not working is : > mount host:/path some-local-path > > which should

Re: Can't NFS mount ZFS volume

2017-10-01 Thread Rick Macklem
Michael Butler wrote: > I have no idea why but using .. > > sudo /sbin/mount vm01:/usr/local/exports/ /mnt This is weird. I would have thought they would both result in the same behaviour. > .. instead of .. > > sudo /sbin/mount -t nfs vm01:/usr/local/exports/ /mnt Did this work with the older

Re: Can't NFS mount ZFS volume

2017-09-30 Thread Rick Macklem
I have only done two NFS commits within that range. 1 - A trivial one that adds two new arguments always specified as 0, which has no change in semantics. 2 - One that only affects NFSv4 during dismount, so it shouldn't affect an NFSv3 mount. Some things to try: - get rid of rpc.statd

anyone in the Boston area with time this week?

2017-09-24 Thread Rick Macklem
Hi, I really doubt that there is anyone out there interested in doing this, but I figured it can't hurt asking... RedHat is hosting a NFSv4 testing event at their facility at 34 Littleton Rd Westford, MA 01186 next week. There is no fee for attendance, but you need to physically be there

adding flex file layout support to the pNFS client

2017-09-18 Thread Rick Macklem
Hi, I now have a series of patches that adds Flex File layout support to the NFSv4 client for pNFS. I am now thinking about how to get them into head. 1 - I could put them up on reviews.freebsd.org, but since they are purely NFS patches and there is no Flex file layout server to test

Re: anyone had experience expanding uid_t and gid_t?

2017-08-22 Thread Rick Macklem
On 19/8/17 11:15 am, Julian Elischer wrote: >> at $JOB there are clients where 32bits is starting to chafe. >> >> Has anyone expanded them? >> >Other than a few offline comments I haven't heard anyone directly >respond to this. >Does anyone have any comments on feasibility or suggestions? >NFSV3

NFSv4 server configs may need nfsuserd_enable="YES"

2017-07-28 Thread Rick Macklem
As of r321665, an NFSv4 server configuration that supports NFSv4 Kerberos mounts or NFSv4 clients that do not support the uid/gid in the owner/owner_group string will need to have: nfsuserd_enable="YES" in the machine's /etc/rc.conf file. The background to this is that the capability to put

Re: small patch for /etc/rc.d/nfsd, bugfix or POLA violation?

2017-07-11 Thread Rick Macklem
Cy Schubert wrote: >Rick Macklem wrote: >> Hi, >> >> The attached one line patch to /etc/rc.d/nfsd modifies the script so that i= >> t >> does not force the nfsuserd to be run when nfsv4_server_enable is set. >> (nfsuserd can still be enabled via

small patch for /etc/rc.d/nfsd, bugfix or POLA violation?

2017-07-09 Thread Rick Macklem
Hi, The attached one line patch to /etc/rc.d/nfsd modifies the script so that it does not force the nfsuserd to be run when nfsv4_server_enable is set. (nfsuserd can still be enabled via nfsuserd_enable="YES" is /etc/rc.conf.) Here's why I think this patch might be appropriate... (a) - The

  1   2   3   4   5   >