Re: files disappearing from ls on NFS

Daniel Braniss wrote: > > Hartmut Brandt wrote: > > > Hi, > > > > > > I've updated one of my -current machines this week (previous > > > update > > > was in > > > february). Now I see a strange effect (it seems only on NFS > > > mounts): > > > ls or > > > even echo * will list only some files (stra

Re: files disappearing from ls on NFS

Hartmut Brandt wrote: > Hi, > > I've updated one of my -current machines this week (previous update > was in > february). Now I see a strange effect (it seems only on NFS mounts): > ls or > even echo * will list only some files (strange enough the first files > from > the normal, alphabetically or

Re: newnfs pkgng database corruption?

Baptiste Daroussin wrote: > On Fri, Apr 12, 2013 at 12:56:10PM +, Eggert, Lars wrote: > > Hi, > > > > On Apr 12, 2013, at 1:10, Rick Macklem wrote: > > > Well, I have no idea why an NFS server would reply errno 70 if the > > > file > > > st

Re: newnfs pkgng database corruption?

Lars Eggert wrote: > Hi, > > On Apr 11, 2013, at 1:28, Rick Macklem wrote: > > Error code 70 is ESTALE (or NFSERR_STALE, if you prefer). The server > > replies with that when the file no longer exists. > > > > File locking doesn't stop a file from being r

Re: newnfs pkgng database corruption?

Lars Eggert wrote: > Hi, > > on a diskless server, I keep the ports tree and pkgng databases on a > newnfs NFSv4 mount. After a bunch of "portmaster -a" runs, the pkgng > sqlite database appears to get corrupted. For example, when I try to > update an existing port, this happens: > > root@five:~

Re: Possible bug in NFSv4 with krb5p security?

Andrey Simonenko wrote: > On Wed, Feb 20, 2013 at 06:29:07PM -0500, Rick Macklem wrote: > > Andrey Simonnenko wrote: > > > > > > Another variant. This is a program that can be used for verifying > > > correctness of the function, just change PWBUF_SIZE_* values

Re: Strange error when compiling minimal GSSAPI application

Benjamin Kaduk wrote: > On Sat, 16 Mar 2013, Rick Macklem wrote: > > > Elias Martenson wrote: > > > >> Is there a problem with the GSSAPI implementation in FreeBSD? > >> > >> I'm trying to compile a minimal application that does nothing more >

Re: Strange error when compiling minimal GSSAPI application

Elias Martenson wrote: > Is there a problem with the GSSAPI implementation in FreeBSD? > > I'm trying to compile a minimal application that does nothing more > than > including the file gssapi/gssapi_krb5.h: > If you add: #include it compiles. in included by krb5.h, which I suspect most prog

Re: NewNFS vs. oldNFS for 10.0?

Andre Oppermann wrote: > On 15.03.2013 15:01, Eggert, Lars wrote: > > Hi, > > > > this reminds me that I ran into an issue lately with the new NFS and > > locking for NFSv3 mounts on a client that ran -CURRENT and a server > > that ran > > -STABLE. > > > > When I ran "portmaster -a" on the client,

Re: NewNFS vs. oldNFS for 10.0?

Peter Wemm wrote: > On Fri, Mar 15, 2013 at 2:03 PM, John Baldwin wrote: > > On Friday, March 15, 2013 11:24:32 am Andre Oppermann wrote: > >> On 15.03.2013 14:46, John Baldwin wrote: > >> > On Friday, March 15, 2013 9:40:56 am Andre Oppermann wrote: > >> >> Hi Rick, all, > >> >> > >> >> is there

Re: NewNFS vs. oldNFS for 10.0?

Freddie Cash wrote: > Isn't the general process (or at least past pattern) to: > - have 1 release cycle with just the old code (aka 8.x with oldNFS) > - have 1 release cycle with old and new code, default to old (aka 9.x > with oldNFS + newNFS) Actually, your numbering is out by one. 7.x - old only

Re: NewNFS vs. oldNFS for 10.0?

John Baldwin wrote: > On Friday, March 15, 2013 11:24:32 am Andre Oppermann wrote: > > On 15.03.2013 14:46, John Baldwin wrote: > > > On Friday, March 15, 2013 9:40:56 am Andre Oppermann wrote: > > >> Hi Rick, all, > > >> > > >> is there a plan to decide for one NFS implementation for FreeBSD > > >

Re: NewNFS vs. oldNFS for 10.0?

Alfred Perlstein wrote: > On 3/15/13 10:55 AM, Adrian Chadd wrote: > > On 15 March 2013 09:55, Alfred Perlstein wrote: > > > >> Finally, I think it is really premature to declare a sunset for the > >> oldnfs > >> until the users are gushing with approval over the new system. > > The flipside to th

Re: NewNFS vs. oldNFS for 10.0?

Lars Eggert wrote: > Hi, > > this reminds me that I ran into an issue lately with the new NFS and > locking for NFSv3 mounts on a client that ran -CURRENT and a server > that ran -STABLE. > > When I ran "portmaster -a" on the client, which mounted /usr/ports and > /usr/local, as well as the locat

Re: NewNFS vs. oldNFS for 10.0?

Andre Oppermann wrote: > Hi Rick, all, > > is there a plan to decide for one NFS implementation for FreeBSD 10.0, > or to keep both around indefinately? > > I'm talking about: > oldNFS in sys/{nfs, nfsclient, nfsserver} NFSv2+NFSv3 > newNFS in sys/fs/{nfs, nfsclient, nfsserver} NFSv2+NFSv3+NFSv4

Re: Possible bug in NFSv4 with krb5p security?

Andrey Simonnenko wrote: > On Tue, Feb 19, 2013 at 08:52:49PM -0500, Rick Macklem wrote: > > > > > > I cannot find how to get information about maximum buffer size for > > > the getpwnam_r() function. This information should be returned by > > > sysconf(_SC_G

Re: Possible bug in NFSv4 with krb5p security?

Andrey Simonenko wrote: > On Tue, Feb 19, 2013 at 05:35:50PM +0800, Elias Martenson wrote: > > On 19 February 2013 17:31, Andrey Simonenko > > wrote: > > > > It can require bigger buffer, since root can get the pw_password > > field > > > in the struct passwd{}. > > > > > > Since sysconf(_SC_GETPW_

Re: Possible bug in NFSv4 with krb5p security?

Elias Martenson wrote: > On 17 February 2013 22:58, Rick Macklem wrote: > > I think the Makefiles are in the kerberos5 directory. > > > > Since the only function you care about is the one in > > kerberos5/lib/libgssapi_krb5/pname_to_uid.c, I'd > > just pu

Re: Possible bug in NFSv4 with krb5p security?

Elias Martenson wrote: > On 17 February 2013 02:17, Doug Rabson wrote: > > > > > I think it was Rick that mentioned the patch. I would apply the > > patch and > > rebuild your kernel in the interests of changing as little as > > possible > > while debugging the original issue. > > > > Fair enoug

Re: Possible bug in NFSv4 with krb5p security?

Doug Rabson wrote: > On 16 February 2013 13:57, Elias Mårtenson wrote: > > > On 16 February 2013 18:58, Doug Rabson wrote: > > > >> This may be a stupid question but does the user 'elias' exist in > >> the > >> local password database? > >> > >> If you are using heimdal from the base distributio

Re: Possible bug in NFSv4 with krb5p security?

Benjamin Kaduk wrote: > On Sat, 16 Feb 2013, Elias Mårtenson wrote: > > > > > Thank you. I did exactly that and I found out some more. > > > > The problem occurss in file gss.c, in the > > function gssd_pname_to_uid_1_svc(). This function is responsible for > > taking > > a principal and returning

Re: Possible bug in NFSv4 with krb5p security?

Elias Martenson wrote: > Thank you for your help. I'm currently in the process of analysing > what is happening inside gssd during these operations. I'll get back > later with a summary of my findings. > > > However, I have found a real bug this time. An honest to FSM kernel > crash. This is how

Re: Possible bug in NFSv4 with krb5p security?

o_uid in it that does the translation. It basically does a gss_pname_to_uid() followed by a getpwuid() to do the translation from principal name to uid + gid list. If this fails, then it maps uid == 65534, which is usually "nobody". (Why does the code has 65534 hardwired in it? I have no idea

Re: Possible bug in NFSv4 with krb5p security?

Elias Martenson wrote: > On 12 February 2013 23:20, Rick Macklem < rmack...@uoguelph.ca > > wrote: > > > > > > > There is (in case you missed it on google): > http://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup > (Nothing much has changed

Re: Possible bug in NFSv4 with krb5p security?

Elias Martenson wrote: > First of all, I used the "bug" word in the subject, and I'm not doing > that > lightly. I fully understand that the initial reaction to such claim is > "he > did something wrong", and frankly, that's what I'm hoping. > > I've spent the last two weeks trying to get an NFS s

Re: panic: LK_RETRY set with incompatible flags

Sergey Kandaurov wrote: > Sergey Kandaurov wrote: > > On 7 February 2013 19:42, Andriy Gapon wrote: > > > on 07/02/2013 17:36 Sergey Kandaurov said the following: > > >> I tested the patch without the (*vpp != dvp) change. > > >> It works well. > > >> > > >> It's something unrelated but when doing

Re: panic: LK_RETRY set with incompatible flags

Sergey Kandaurov wrote: > On 7 February 2013 19:42, Andriy Gapon wrote: > > on 07/02/2013 17:36 Sergey Kandaurov said the following: > >> I tested the patch without the (*vpp != dvp) change. > >> It works well. > >> > >> It's something unrelated but when doing ls -l > >> on server (patched) and cl

Re: panic: LK_RETRY set with incompatible flags

Andriy Gapon wrote: > on 07/02/2013 17:04 Rick Macklem said the following: > > The other thing I wondered about is "can zfsvfs->z_shares_dir ever > > not > > fit in 32bits?". > > Usually it should be one of the first objects created in a new > filesystem

Re: panic: LK_RETRY set with incompatible flags

Andriy Gapon wrote: > on 07/02/2013 04:13 Rick Macklem said the following: > > Andriy Gapon wrote: > >> on 06/02/2013 17:15 Rick Macklem said the following: > >>> Well, zfs_vget() returns EOPNOTSUPP for .zfs, so the NFS server > >>> knows to > >&

Re: panic: LK_RETRY set with incompatible flags

Andriy Gapon wrote: > on 06/02/2013 17:15 Rick Macklem said the following: > > Well, zfs_vget() returns EOPNOTSUPP for .zfs, so the NFS server > > knows to > > switch over to using VOP_LOOKUP(). If the .zfs/snapshot and > > .zfs/share > > do the same thing, that

Re: panic: LK_RETRY set with incompatible flags

Andriy Gapon wrote: > on 06/02/2013 03:30 Rick Macklem said the following: > > Since I don't understand ZFS, I have just posted a query on > > freebsd-fs@, which I hope will get noticed by people who > > may know why ZFS is doing this. > > Actually I think I hav

Re: panic: LK_RETRY set with incompatible flags

Sergey Kandaurov wrote: > On 5 February 2013 04:13, Rick Macklem wrote: > > Sergey Kandaurov wrote: > >> On 4 February 2013 06:32, Rick Macklem > >> wrote: > >> > Konstantin Belousov wrote: > >> >> On Sat, Feb 02, 2013 at 09:30:39PM -

Re: panic: LK_RETRY set with incompatible flags

Sergey Kandaurov wrote: > On 4 February 2013 06:32, Rick Macklem wrote: > > Konstantin Belousov wrote: > >> On Sat, Feb 02, 2013 at 09:30:39PM -0500, Rick Macklem wrote: > >> > Andriy Gapon wrote: > >> > > on 31/01/2013 15:29 Serge

Re: panic: LK_RETRY set with incompatible flags

Sergey Kandaurov wrote: > On 4 February 2013 16:30, Sergey Kandaurov wrote: > > On 4 February 2013 16:13, Sergey Kandaurov > > wrote: > >> On 4 February 2013 16:06, Andriy Gapon wrote: > >>> on 04/02/2013 13:49 Sergey Kandaurov said the following: > Hi, Rick! Here is the requested info rega

Re: panic: LK_RETRY set with incompatible flags

Konstantin Belousov wrote: > On Sat, Feb 02, 2013 at 09:30:39PM -0500, Rick Macklem wrote: > > Andriy Gapon wrote: > > > on 31/01/2013 15:29 Sergey Kandaurov said the following: > > > > Hi. > > > > > > > > Got this assertion on idle NFS server

Re: panic: LK_RETRY set with incompatible flags

Konstantin Belousov wrote: > On Sat, Feb 02, 2013 at 09:30:39PM -0500, Rick Macklem wrote: > > Andriy Gapon wrote: > > > on 31/01/2013 15:29 Sergey Kandaurov said the following: > > > > Hi. > > > > > > > > Got this assertion on idle NFS server

Re: panic: LK_RETRY set with incompatible flags

Andriy Gapon wrote: > on 03/02/2013 18:36 Rick Macklem said the following: > > I can think of two possibilities: > > 1 - ZFS isn't setting VV_ROOT on the root vnode under some > > condition. > > or > > 2 - The vnode was left locked from some previous operatio

Re: panic: LK_RETRY set with incompatible flags

Konstantin Belousov wrote: > On Sat, Feb 02, 2013 at 09:30:39PM -0500, Rick Macklem wrote: > > Andriy Gapon wrote: > > > on 31/01/2013 15:29 Sergey Kandaurov said the following: > > > > Hi. > > > > > > > > Got this assertion on idle NFS server

Re: panic: LK_RETRY set with incompatible flags

Andriy Gapon wrote: > on 31/01/2013 15:29 Sergey Kandaurov said the following: > > Hi. > > > > Got this assertion on idle NFS server while `ls -la /.zfs/shares/' > > issued on NFS client. > > kern/vfs_vnops.c:_vn_lock() > > KASSERT((flags & LK_RETRY) == 0 || error == 0, > >

Re: mounting root from NFS via ROOTDEVNAME

Lars Eggert wrote: > Hi, > > On Jan 30, 2013, at 22:43, Craig Rodrigues > wrote: > > What you need to do is, before the FreeBSD kernel boots, your > > loader needs to export some environment variables. This will trigger > > the various behaviors in the FreeBSD mount code. > > the loader can expo

Re: mounting root from NFS via ROOTDEVNAME

Lars Eggert wrote: > Hi, > > On Jan 29, 2013, at 20:22, Craig Rodrigues > wrote: > > What kind of architecture are you trying to do this on? Is this > > i386/amd64 or something else? > > amd64 > > > I am not familiar with netboot compared to > > PXE. Is TFTP involved at all with netboot? > >

Re: mounting root from NFS via ROOTDEVNAME

Lars Eggert wrote: > Hi, > > I'm trying to netboot a system where the root device is specified in > the kernel via ROOTDEVNAME: > > options BOOTP > options BOOTP_NFSROOT > options BOOTP_NFSV3 > options BOOTP_COMPAT > options BOOTP_WIRED_TO=em4 > options ROOTDEVNAME=\"nfs:10.11.12.13:/usr/home/ela

Re: sysctl -a causes kernel trap 12

d wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 1/7/13 5:33 PM, Brandon Gooch wrote: > > On Mon, Jan 7, 2013 at 6:09 PM, Xin Li > > wrote: > > > > -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > > > > On 01/07/13 16:02, Konstantin Belousov wrote:

Re: ZFS/RAIDZ and SAMBA: abyssimal performance

Fabian Keil wrote: > Fleuriot Damien wrote: > > > > > On Jan 4, 2013, at 4:19 PM, O. Hartmann > > wrote: > > > > > Am 01/04/13 15:45, schrieb Garrett Cooper: > > >> On Fri, Jan 4, 2013 at 6:06 AM, Fleuriot Damien wrote: > > >> > > >> ... > > >> > > >>> And this is under [global] in /usr/local/e

Re: r245005M: NFSv4 usermapping not working anymore

O. Hartmann wrote: > Since yesterday's update and buildworld on two FreeBSD 10.0-CURRENT > boxes, i realize a strange behaviour. I have one server exporting via > NFSv4 several ZFS volumes. The UID mapping went pretty well so far, > but > with a reboot of yesterday (after a buildworld), files are s

Re: Amd(8) Hangs at Boot

Cy Schubert wrote: > Just udated to the latest current and amd hangs at boot. Ideas? > I think I spoke too soon w.r.t. the bxe(4) device and UDP checksums. I thought I saw some email about UDP checksum offload for it being broken but I can't locate the email, so I probably have this wrong. Sorry

Re: Amd(8) Hangs at Boot

Cy Schubert wrote: > Just udated to the latest current and amd hangs at boot. Ideas? > It appears that r244678 broke the ip4 configuration of loopback for some network interfaces. I don't know, but it might explain why this is happening? Also, if you happen to have a bxe(4) interface, it looks l

Re: svn commit: r244604 - head/usr.sbin/gssd

Rick Macklem wrote: > Rick Macklem wrote: > > Garrett Cooper wrote: > > > On Sun, Dec 30, 2012 at 4:49 PM, Rick Macklem > > > > > > wrote: > > > > bf1783 wrote: > > > >> >Author: rmacklem > > > >> &

Re: svn commit: r244604 - head/usr.sbin/gssd

Rick Macklem wrote: > Garrett Cooper wrote: > > On Sun, Dec 30, 2012 at 4:49 PM, Rick Macklem > > wrote: > > > bf1783 wrote: > > >> >Author: rmacklem > > >> >Date: Sat Dec 22 23:21:17 2012 > > >> >New Revision

Re: svn commit: r244604 - head/usr.sbin/gssd

Garrett Cooper wrote: > On Sun, Dec 30, 2012 at 4:49 PM, Rick Macklem > wrote: > > bf1783 wrote: > >> >Author: rmacklem > >> >Date: Sat Dec 22 23:21:17 2012 > >> >New Revision: 244604 > >> >URL: http://svnweb.freebsd.org/changeset/bas

Re: svn commit: r244604 - head/usr.sbin/gssd

bf1783 wrote: > >Author: rmacklem > >Date: Sat Dec 22 23:21:17 2012 > >New Revision: 244604 > >URL: http://svnweb.freebsd.org/changeset/base/244604 > > > >Log: > > It was reported via email that some sshds create kerberos > > credential cache files with names other than /tmp/krb5cc_. > > The gss

Re: Amd(8) Hangs at Boot

David Wolfskill wrote: > On Sat, Dec 29, 2012 at 09:38:42AM -0800, Cy Schubert wrote: > > Just udated to the latest current and amd hangs at boot. Ideas? > > > > I don't see a problem @r244855. On my build machine, /usr/ports is a > symlink to a "ports" working copy that resides on a ReadyNAS

r244604 breaks build WITHOUT_KERBEROS + WITH_GSSAPI for gssd.c

Hi, Maybe someone familiar with the build environment can help with this. Someone reported via email that gssd.c no longer builds for the combination of WITHOUT_KERBEROS and WITH_GSSAPI. Now, the gssd is completely useless without kerberos, but I need a way to fix the build for this case? Can i

Re: nfsd won't start on post r243965 kernels without INET6

Oops, I did my usual brain fart again and forgot to attach the patch. Here it is, rick - Original Message - > Just fyi, r243965 introduced a minor pola violation where the > nfsd daemon won't start for kernels built without "options INET6". > > The attached patch, which I will commit to h

nfsd won't start on post r243965 kernels without INET6

Just fyi, r243965 introduced a minor pola violation where the nfsd daemon won't start for kernels built without "options INET6". The attached patch, which I will commit to head later to-day, fixes the problem. (Or you can add "options INET6" to your kernel config.) Reported and tested by avg@. r

Re: r244036 kernel hangs under load.

Konstantin Belousov wrote: > On Wed, Dec 12, 2012 at 10:01:39PM -0500, Rick Macklem wrote: > > Konstantin Belousov wrote: > > > On Tue, Dec 11, 2012 at 08:58:47PM -0500, Rick Macklem wrote: > > > > Ok, I'll test r243598 and then r243599 and r243835, just

Re: r244036 kernel hangs under load.

Konstantin Belousov wrote: > On Wed, Dec 12, 2012 at 10:01:39PM -0500, Rick Macklem wrote: > > Konstantin Belousov wrote: > > > On Tue, Dec 11, 2012 at 08:58:47PM -0500, Rick Macklem wrote: > > > > Ok, I'll test r243598 and then r243599 and r243835, just

Re: r244036 kernel hangs under load.

Konstantin Belousov wrote: > On Tue, Dec 11, 2012 at 08:58:47PM -0500, Rick Macklem wrote: > > Ok, I'll test r243598 and then r243599 and r243835, just to > > see if it really is this. > > > > I'll email when I have done this. > If you test only r243

Re: r244036 kernel hangs under load.

Konstantin Belousov wrote: > On Tue, Dec 11, 2012 at 05:30:24PM -0500, Rick Macklem wrote: > > Konstantin Belousov wrote: > > > On Tue, Dec 11, 2012 at 04:55:52PM -0500, Rick Macklem wrote: > > > > Konstantin Belousov wrote: > > > > > On Mon, Dec 10,

Re: r244036 kernel hangs under load.

Konstantin Belousov wrote: > On Tue, Dec 11, 2012 at 04:55:52PM -0500, Rick Macklem wrote: > > Konstantin Belousov wrote: > > > On Mon, Dec 10, 2012 at 07:11:59PM -0500, Rick Macklem wrote: > > > > Konstantin Belousov wrote: > > > > > On Mon, Dec 10,

Re: r244036 kernel hangs under load.

Konstantin Belousov wrote: > On Mon, Dec 10, 2012 at 07:11:59PM -0500, Rick Macklem wrote: > > Konstantin Belousov wrote: > > > On Mon, Dec 10, 2012 at 01:38:21PM -0500, Rick Macklem wrote: > > > > Adrian Chadd wrote: > > > > > .. what was the previou

Re: r244036 kernel hangs under load.

Konstantin Belousov wrote: > On Mon, Dec 10, 2012 at 01:38:21PM -0500, Rick Macklem wrote: > > Adrian Chadd wrote: > > > .. what was the previous kernel version? > > > > > Hopefully Tim has it narrowed down more, but I don't see > > the hangs on a Sept.

Re: r244036 kernel hangs under load.

Adrian Chadd wrote: > .. what was the previous kernel version? > Hopefully Tim has it narrowed down more, but I don't see the hangs on a Sept. 7 kernel from head and I do see them on a Dec. 3 kernel from head. (Don't know the eact rNN.) It seems to predate my commit (r244008), which was my fi

Heads Up: NFSv4.1 patch going into head

I don't believe the patch I just committed to head for the kernel RPC to add backchannel support or the NFS client patch coming soon should affect operation unless the new "minorversion=1" is used. However, since the patch is fairly large, I thought I'd give everyone a "head up", in case it someho

Re: ZFS: ZIL with only one additional disk and how secure?

Olivier Smedts wrote: > Hi, > > 2012/11/28 O. Hartmann : > > Hello, > > I have a naive question. > > I read about speeding up NFSv4 shared ZFS array. I use a RAIDZ1 > > volume > > made up from 5 times 3TB harddrives, attached to a ICH10 SATA > > controller > > on a FreeBSD 10.0-CURRENT box. The ma

Re: svn MFC to stable/8

John Baldwin wrote: > On Thursday, October 04, 2012 2:10:11 pm Rick Macklem wrote: > > Hi, > > > > Hopefully someone familiar with svn can help. When I try to MFC > > a kernel change to stable/8, it works, but I end up with tons of > > mergeinfo. (It loo

Re: svn MFC to stable/8

Sean Bruno wrote: > On Thu, 2012-10-04 at 11:10 -0700, Rick Macklem wrote: > > Hi, > > > > Hopefully someone familiar with svn can help. When I try to MFC > > a kernel change to stable/8, it works, but I end up with tons of > > mergeinfo. (It looks like every d

svn MFC to stable/8

Hi, Hopefully someone familiar with svn can help. When I try to MFC a kernel change to stable/8, it works, but I end up with tons of mergeinfo. (It looks like every directory under sys.) Does this matter or is there a trick to avoid this? Thanks in advance for any help, rick ps: I seem to MFC fi

open-sshd uses non-default Kerberos cred cache breaking Kerberized NFS

r does anyone know if there is an easy way to tell open-sshd to use the default credential cache file name? If not, all I can think of is to document this in gssd.8. Thanks in advance for any help with this, rick [Herbert Poeckl wrote in an email to me, copied with his permission] > Hi Ric

Re: Occassional "permission denied" in the middle of a large transfer over NFS

Vincent Hoffman: > On 08/07/2012 00:26, Rick Macklem wrote: > > Vincent Hoffman wrote: > >> > >> Hi Rick, > >> > >> I'm afraid this didnt make any real difference for me. > >> Since I couldnt test it on the live system I tried it on a

Re: Occassional "permission denied" in the middle of a large transfer over NFS

Vincent Hoffman wrote: > On 07/07/2012 13:26, Vincent Hoffman wrote: > > On 01/07/2012 12:18, Rick Macklem wrote: > >> Vincent Hoffman wrote: > >>> On 01/07/2012 01:53, Rick Macklem wrote: > >>>> To modify mountd to use the kernel changes is more wor

Re: Occassional "permission denied" in the middle of a large transfer over NFS

Vincent Hoffman wrote: > On 01/07/2012 12:18, Rick Macklem wrote: > > Vincent Hoffman wrote: > >> On 01/07/2012 01:53, Rick Macklem wrote: > >>> To modify mountd to use the kernel changes is more work than I > >>> have > >>> time for,

Re: Occassional "permission denied" in the middle of a large transfer over NFS

Vincent Hoffman wrote: > On 01/07/2012 01:53, Rick Macklem wrote: > > Vincent Hoffman wrote: > >> Just a note to say I have tested this on -CURRENT with the new nfs > >> server and it is still the case. > >> > >> On the client (FreeBSD seaurchin 8.3-R

Re: Occassional "permission denied" in the middle of a large transfer over NFS

Vincent Hoffman wrote: > Just a note to say I have tested this on -CURRENT with the new nfs > server and it is still the case. > > On the client (FreeBSD seaurchin 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 > #0: Tue Jun 12 00:39:29 UTC 2012 > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GEN

Re: FreeBSD 10 prognostication...

Jamie wrote: > On Thu, May 17, 2012 at 07:20:18PM -0400, Vance Siemens wrote: > > Eh, sorry. I got excited at the prospect of downloading FreeBSD from > > the App Store and having the installer "just work" in a modern GUI. > > You have to admit, FreeBSD is lacking in this area. It would be a > > bo

Re: r235163: root: /etc/rc.d/sysctl: WARNING: sysctl vfs.nfs.access_cache_timeout does not exist.

Anton Shterenlikht wrote: > On Thu, May 10, 2012 at 09:51:22PM +0100, Anton Shterenlikht wrote: > > On Thu, May 10, 2012 at 06:11:28PM +0400, Sergey Kandaurov wrote: > > > On 10 May 2012 14:30, Anton Shterenlikht > > > wrote: > > > > > > > > On ia64 r235163: > > > > > > > > root: /etc/rc.d/sysctl:

Re: mountd, rpc.lockd and rpc.statd patches for testing

Andrey Simonenko wrote: > On Mon, May 30, 2011 at 04:56:02PM -0400, Rick Macklem wrote: > > Hi, > > > > I have patches for the mountd, rpc.statd and rpc.lockd daemons > > that are meant to keep them from failing when a dynamically > > selected port# is not

Re: posix_fadvise noreuse disables file caching

John Baldwin wrote: > On Tuesday, January 31, 2012 12:21:07 pm Ulrich Spörlein wrote: > > On Mon, 2012-01-30 at 09:36:45 -0500, John Baldwin wrote: > > > On Sunday, January 29, 2012 10:08:10 am Tijl Coosemans wrote: > > > > On Wednesday 25 January 2012 17:29:22 John Baldwin wrote: > > > > > On Frid

Heads Up: NFS clients can now fail "mount -u -o udp..."

Hi, r230516, which was just committed to head/current, will result in a "mount -u -o udp /path" failing if the mount is using an rsize/wsize/readdirsize of greater than 16384 (which will be the case of a default sized TCP mount). As such, specifying "udp" or "mntudp" options in the /etc/fstab ent

Re: amd: is there an alternative with NFSv4 capabilities?

O. Hartmann wrote: > Hello. > I still use the amd automounter, but I miss NFSv4 capabilities. Since > Linux seems to use a more deep in the kernel located facility, I'd > like > to ask whether FreeBSd has an alternative to the amd automounter with > NFSv4 capabilities. Sorry if I bother someone, I'

Re: Data corruption over NFS in -current

Martin Cracauer wrote: > More findings. > > Reminder, with the original report I found: > - files for no reason changing ownership and group to > root/ > - data corruption as in inserting binary junk obviously from ports > - data corruption as in malformed ascii text that might be a bug I > have i

Re: Data corruption over NFS in -current

Martin Cracauer wrote: > More findings. > > Reminder, with the original report I found: > - files for no reason changing ownership and group to > root/ > - data corruption as in inserting binary junk obviously from ports > - data corruption as in malformed ascii text that might be a bug I > have i

Re: Data corruption over NFS in -current

Martin Cracauer wrote: > Stefan Bethke wrote on Wed, Jan 11, 2012 at 07:14:44PM +0100: > > Am 11.01.2012 um 17:57 schrieb Martin Cracauer: > > > > > I'm sorry for the unspecific bug report but I thought a heads-up > > > is > > > better than none. > > > > > > $ uname -a > > > FreeBSD wings.cons.org

Re: re(4) driver dropping packets when reading NFS files

Way back in Nov 2010, this thread was related to a problem I had, where an re(4) { 810xE PCIe 10/100baseTX, according to the driver } interface dropped received packets, resulting in a significant impact of NFS performance. Well, it turns out that a recent (post r224506) commit seems to have fixed

license question w.r.t. NFSv4.1 Layout drivers - calling all amateur lawyers

First off, I had no idea which mailing list would be appropriate for this, so apologies in advance if I chose the wrong one. For NFSv4.1 pNFS, there are layout drivers in Linux that I would like to reuse for the FreeBSD client. (Re-writing these drivers from scratch would be a lot of work and diff

Re: making crdup()/crcopy() safe??

John Baldwin wrote: > On Monday, December 19, 2011 8:21:45 pm Rick Macklem wrote: > > Hi, > > > > A recent NFS client crash: > > http://glebius.int.ru/tmp/nfs_panic.jpg > > appears to have happened because some field is > > bogus when crfree() is called. I&

making crdup()/crcopy() safe??

Hi, A recent NFS client crash: http://glebius.int.ru/tmp/nfs_panic.jpg appears to have happened because some field is bogus when crfree() is called. I've asked Gleb to disassemble crfree() for me, so I can try and see exactly which field causes the crash, however... Basically, the code: newc

Re: multihomed nfs server - NLM lock failure on additional interfaces

John De wrote: > Hi Folks, > > I have a 9-prerelease system where I've been testing nfs/zfs. The > system has been working quite well until moving the server to a > multihomed > configuration. > > Given the following: > > nfsd: master (nfsd) > nfsd: server (nfsd) > /usr/sbin/rpcbind -h 10.24.6.3

Re: NFS + SVN problem?

Dimitry Andric wrote: > On 2011-11-23 19:26, Sean Bruno wrote: > > On Wed, 2011-11-23 at 09:58 -0800, Rick Macklem wrote: > >> I don't know if Dimitry tried this, but you could also try the > >> "nolockd" option, so that byte range locking is done loc

Re: F_RDLCK lock to FreeBSD NFS server fails to R/O target file (nasty little bug)

John wrote: > After pondering the best way to allow the VOP_ACCESS() call to > only query for the permissions really needed, I've come up with > a patch that minimally adds one parameter to the nlm_get_vfs_state() > function call with the lock type from the original argp. > > http://people.freebsd

Re: F_RDLCK lock to FreeBSD NFS server fails to R/O target file [PATCH]

John wrote: > After pondering the best way to allow the VOP_ACCESS() call to > only query for the permissions really needed, I've come up with > a patch that minimally adds one parameter to the nlm_get_vfs_state() > function call with the lock type from the original argp. > > http://people.freebsd

Re: zfs i/o hangs on 9-PRERELEASE

Pawel Jakub Dawidek wrote: > On Fri, Nov 25, 2011 at 01:20:01PM -0600, Mark Felder wrote: > > 13:14:32 nas:~ > uname -a > > FreeBSD nas.feld.me 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #3 > > r227971M: > > Fri Nov 25 10:07:48 CST 2011 > > r...@nas.feld.me:/usr/obj/tank/svn/sys/GENERIC amd64 > > > > Th

Re: NFSV4 readlink_stat

erisk.sunsaturn.com:/usr/obj/usr/src/sys/MYKERNEL amd64 > > > Can view either file here: > > http://www.sunsaturn.com/nfsv4/nfs.txt (raw dump) > http://www.sunsaturn.com/nfsv4/nfs2.txt (-r dump) > > > > Dan. > > > -- > Dan The Man > CTO/ Senio

Re: NFS + SVN problem?

Sean Bruno wrote: > On Wed, 2011-11-23 at 09:58 -0800, Rick Macklem wrote: > > I don't know if Dimitry tried this, but you could also try the > > "nolockd" option, so that byte range locking is done locally in > > the client and avoids the NLM. > > > &

Re: NFS + SVN problem?

Dimitry Andric wrote: > On 2011-11-23 17:41, Sean Bruno wrote: > > Not sure what this all means, but when I attempt to check out HEAD > > on an > > NFS mount in the fbsd cluster (nfs server is a netapp filer), I'm > > getting an odd failure error. > > > > > > FreeBSD bhyve.freebsd.org 10.0-CURRENT

Re: NFS + SVN problem?

Dinitry Andric wrote: > On 2011-11-23 17:41, Sean Bruno wrote: > > Not sure what this all means, but when I attempt to check out HEAD > > on an > > NFS mount in the fbsd cluster (nfs server is a netapp filer), I'm > > getting an odd failure error. > > > > > > FreeBSD bhyve.freebsd.org 10.0-CURRENT

Re: NFS + SVN problem?

Sean Bruno wrote: > Not sure what this all means, but when I attempt to check out HEAD on > an > NFS mount in the fbsd cluster (nfs server is a netapp filer), I'm > getting an odd failure error. > > > FreeBSD bhyve.freebsd.org 10.0-CURRENT FreeBSD 10.0-CURRENT #0 > r227883: > Wed Nov 23 06:08:40

Heads Up: NFS server will now use LK_SHARED vnode locks

Hi, I have just committed r227809 to head/current which enables the new/default NFS server's use of shared vnode locks for Read, Readdir, Readlink, Getattr and Access. Although it is hoped that this will improve performance for these operations when multiple ones are performed concurrently on the

Re: NFSV4 readlink_stat

Dan The Man wrote: > Just want to include some errors from rsync trying to copy files using > NFSV4. These files copy fine using NFSV3 > > > rsync: readlink_stat("/asterisk/public/mp3/Kass Tunes/A-E/A/Ace of > Base/The Bridge/Ace of Base-My D\#351j\#340 Vu-09-The Bridge.wma") > failed: > Inva

Re: mtx_lock() of destroyed mutex on NFS

Bjoern A. Zeeb wrote: > Hi, > > as a result of a make buildkernel && make installkernel && reboot all > on NFS I got this with a HEAD SVN source at r226465. I cannot dump > unfortunately and it seems I just killed the obj tree for this kernel > though it should be very close. > > Oct 18 10:03:22

<    1   2   3   4   5   6   7   8   >