From: "J. Bruce Fields" <bfields@fieldses.org>
To: Martin Vogt <martin.vogt@itwm.fraunhofer.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: permission denied with >= ~2.6.25
Date: Wed, 19 May 2010 13:13:47 -0400 [thread overview]
Message-ID: <20100519171347.GB8137@fieldses.org> (raw)
In-Reply-To: <4BF3C7A4.8030906@itwm.fraunhofer.de>
On Wed, May 19, 2010 at 01:12:36PM +0200, Martin Vogt wrote:
> Martin Vogt wrote:
> > Hello,
> >
> >
> > today I tried 2.6.34 on server/client with standard
> > hardware. After around the 69th checkout I had an
> > "Invalid cross-device link" Error.
> > (Before that it was EIO/EPERM)
> >
> > Test ran for around 9 hours before it failed.
> >
> >> svn: In directory 'Kernel-pxe3-69.EZvgHTmbzv/include/asm-sparc'
> >> svn: Can't move
> > 'Kernel-pxe3-69.EZvgHTmbzv/include/asm-sparc/resource.h.tmp'
> >> to 'Kernel-pxe3-69.EZvgHTmbzv/include/asm-sparc/resource.h': Invalid
> >> cross-device link
> >> Mon May 17 23:46:32 CEST 2010,1
> >> runcounter: 69
> >
>
> Ok.
> RTFM: no_subtree_check :-(
>
> This option made the checkouts reliable.
Erp. Should have thought of that. It's no longer the default in recent
nfs-utils, for this sort of reason.
(But, note: for anyone exporting directories that aren't mountpoints,
that may expose more of their filesystem than intended.)
--b.
next prev parent reply other threads:[~2010-05-19 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 11:26 permission denied with >= ~2.6.25 Martin Vogt
2010-05-11 11:02 ` Martin Vogt
2010-05-14 9:56 ` Martin Vogt
2010-05-16 17:52 ` Martin Vogt
[not found] ` <20100516175213.GA9225-DA0fgfH9LvLH7LAFlePENYQuADTiUCJX@public.gmane.org>
2010-05-18 8:34 ` Martin Vogt
2010-05-19 11:12 ` Martin Vogt
2010-05-19 17:13 ` J. Bruce Fields [this message]
2010-05-20 9:28 ` Martin Vogt
2010-05-21 17:39 ` J. Bruce Fields
2010-05-25 8:14 ` Martin Vogt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100519171347.GB8137@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=martin.vogt@itwm.fraunhofer.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).