Terrible NFS4 performance: FreeBSD 9.1 + ZFS + AWS EC2
Outback Dingo
outbackdingo at gmail.com
Mon Jul 8 23:04:47 UTC 2013
On Mon, Jul 8, 2013 at 6:22 PM, Rick Macklem <rmacklem at uoguelph.ca> wrote:
> Berend de Boer wrote:
> > >>>>> "Rick" == Rick Macklem <rmacklem at uoguelph.ca> writes:
> >
> > Rick> Please try this patch:
> >
> > Hi Rick,
> >
> > Could you please reroll the patc hagainst 9.1-RELEASE? Not sure what
> > version of FreeBSD you made this for.
> I haven't a clue, either, to be honest;-)
>
> > I have 9.1-RELEASE. Get three
> > failures:
> >
> I don't have a copy of 9.1-RELEASE handy, but here's one for stable/9.
> If that still fails, just email and I'll download 9.1-RELEASE and create
> one for it.
> http://people.freebsd.org/~rmacklem/drc4-stable9.patch
this patches cleanly against 9/stable updated as of 20 mins ago
>
>
> rick
>
> > # patch --check -p0 < ~/drc4.patch
> > Hmm... Looks like a unified diff to me...
> > The text leading up to this was:
> > --------------------------
> > |--- fs/nfsserver/nfs_nfsdcache.c.orig 2013-01-07
> > |09:04:13.000000000 -0500
> > |+++ fs/nfsserver/nfs_nfsdcache.c 2013-03-12 22:42:05.000000000
> > |-0400
> > --------------------------
> > Patching file fs/nfsserver/nfs_nfsdcache.c using Plan A...
> > Hunk #1 succeeded at 160.
> > Hunk #2 succeeded at 216.
> > Hunk #3 succeeded at 271.
> > Hunk #4 succeeded at 357.
> > Hunk #5 succeeded at 370.
> > Hunk #6 succeeded at 381.
> > Hunk #7 succeeded at 396 with fuzz 2.
> > Hunk #8 succeeded at 426.
> > Hunk #9 succeeded at 444.
> > Hunk #10 succeeded at 468.
> > Hunk #11 failed at 476.
> > Hunk #12 failed at 501.
> > Hunk #13 succeeded at 523.
> > Hunk #14 succeeded at 531.
> > Hunk #15 succeeded at 547.
> > Hunk #16 succeeded at 568.
> > Hunk #17 succeeded at 579.
> > Hunk #18 succeeded at 601.
> > Hunk #19 succeeded at 665.
> > Hunk #20 succeeded at 674.
> > Hunk #21 failed at 683.
> > Hunk #22 succeeded at 718.
> > Hunk #23 succeeded at 729.
> > Hunk #24 succeeded at 750.
> > Hunk #25 succeeded at 779.
> > Hunk #26 succeeded at 788.
> > Hunk #27 succeeded at 803.
> > Hunk #28 succeeded at 828.
> > Hunk #29 succeeded at 927.
> > Hunk #30 succeeded at 943.
> > 3 out of 30 hunks failed--saving rejects to
> > fs/nfsserver/nfs_nfsdcache.c.rej
> > Hmm... The next patch looks like a unified diff to me...
> > The text leading up to this was:
> > --------------------------
> > |--- fs/nfsserver/nfs_nfsdport.c.orig 2013-03-02
> 18:19:34.000000000
> > |-0500
> > |+++ fs/nfsserver/nfs_nfsdport.c 2013-03-12 17:51:31.000000000
> > |-0400
> > --------------------------
> > Patching file fs/nfsserver/nfs_nfsdport.c using Plan A...
> > Hunk #1 succeeded at 59 with fuzz 1 (offset -2 lines).
> > Hunk #2 succeeded at 3284 (offset -22 lines).
> > Hunk #3 succeeded at 3351 with fuzz 1 (offset -5 lines).
> > Hmm... The next patch looks like a unified diff to me...
> > The text leading up to this was:
> > --------------------------
> > |--- fs/nfs/nfsport.h.orig 2013-03-02 18:35:13.000000000 -0500
> > |+++ fs/nfs/nfsport.h 2013-03-12 17:51:31.000000000 -0400
> > --------------------------
> > Patching file fs/nfs/nfsport.h using Plan A...
> > Hunk #1 succeeded at 547 (offset -62 lines).
> > Hmm... The next patch looks like a unified diff to me...
> > The text leading up to this was:
> > --------------------------
> > |--- fs/nfs/nfsrvcache.h.orig 2013-01-07 09:04:15.000000000 -0500
> > |+++ fs/nfs/nfsrvcache.h 2013-03-12 18:02:42.000000000 -0400
> > --------------------------
> > Patching file fs/nfs/nfsrvcache.h using Plan A...
> > Hunk #1 succeeded at 41.
> > done
> >
> >
> > I just want to make sure I can apply it cleanly and that it's not a
> > mistake I made when making this work when it doesn't.
> >
> > --
> > All the best,
> >
> > Berend de Boer
> >
> >
> > ------------------------------------------------------
> > Awesome Drupal hosting: https://www.xplainhosting.com/
> >
> >
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
>
More information about the freebsd-fs
mailing list