From: Phil Blundell <pb@pbcl.net>
To: ml@communistcode.co.uk
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: do_root_fs failing on flock command
Date: Tue, 27 Aug 2013 13:16:01 +0100 [thread overview]
Message-ID: <1377605761.28077.4.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <521C969A.30909@communistcode.co.uk>
On Tue, 2013-08-27 at 13:07 +0100, Jack Mitchell wrote:
> Does anyone have any insight to why this may be failing. It mentions a
> bad file descriptor, so I assume it is related to building on an NFS mount.
There's no particular reason that flock() oughtn't to work on NFS. If
you happened to be mounted with -o nolock then you wouldn't get the
correct semantics versus lockers on other hosts, but you shouldn't be
getting -EBADF under any circumstances that I can think of.
If you run flock by hand against a file on the same mount, does it work?
If it fails, what does the output from strace look like?
p.
next prev parent reply other threads:[~2013-08-27 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 12:07 do_root_fs failing on flock command Jack Mitchell
2013-08-27 12:16 ` Phil Blundell [this message]
2013-08-27 12:38 ` Jack Mitchell
2013-08-27 12:21 ` Richard Purdie
2013-08-27 12:31 ` Jack Mitchell
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=1377605761.28077.4.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.org \
/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