From: Nathan Scott <nathans@sgi.com>
To: "Alexander Y. Fomichev" <gluk@php4.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-rc3-bk5: XFS: fcron: could not write() buf to disk: Resource temporarily unavailable
Date: Wed, 9 Feb 2005 12:29:00 +1100 [thread overview]
Message-ID: <20050209012900.GA1140@frodo> (raw)
In-Reply-To: <200502082051.36989.gluk@php4.ru>
On Tue, Feb 08, 2005 at 08:51:36PM +0300, Alexander Y. Fomichev wrote:
> G' day
>
> It looks like XFS broken somewhere in 2.6.11-rc1,
> sadly i can't sand "right" bugreport, some facts only.
> Upgrade to 2.6.11-rc2 makes fcron non-working for me in case of
> crontabs directory is placed on XFS partition.
> When i try to install new crontab fcrontab die with error:
> "could not write() buf to disk: Resource temporarily unavailable"
Is that an O_SYNC write, do you know? Or a write to an inode
with the sync flag set?
> The same time it works with 2.6.10.
I'm chasing down a problem similar to this atm, so far looks like
something in the generic VM code below sync_page_range is giving
back EAGAIN, and that is getting passed back out to userspace by
XFS. Not sure where/why/how its been caused yet though ... I'll
let you know once I have a fix or have found the culprit change.
cheers.
--
Nathan
next prev parent reply other threads:[~2005-02-09 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 17:51 2.6.11-rc3-bk5: XFS: fcron: could not write() buf to disk: Resource temporarily unavailable Alexander Y. Fomichev
2005-02-09 1:29 ` Nathan Scott [this message]
2005-02-09 14:44 ` Alexander Y. Fomichev
2005-02-10 4:54 ` Nathan Scott
2005-02-10 11:51 ` Alexander Y. Fomichev
2005-02-14 2:50 ` Darren Williams
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=20050209012900.GA1140@frodo \
--to=nathans@sgi.com \
--cc=gluk@php4.ru \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.