From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: nginx blocked task when XFS partition is very full
Date: Fri, 02 Sep 2011 08:02:05 -0500 [thread overview]
Message-ID: <4E60D3CD.5030806@hardwarefreak.com> (raw)
In-Reply-To: <3972BA0F-0E95-4758-9DDB-BC6197621C87@ci-info.com>
On 9/2/2011 7:23 AM, Sean Purdy wrote:
> Hi,
>
>
> This is on 2.6.32-32-server from Ubuntu Lucid 10.04 LTS
>
> We have nginx fileserving from four disks on a machine. We're using mogilefs as a distributed file system. We've come across an issue where when the filesystem is very full, and nginx tries to write to it, we get "task blocked for more than 120 seconds" messages from the kernel, nginx hangs and we can no longer access the fs. When a file is uploaded via nginx, nginx writes to a .tmp directory on the disk before moving the file to its destination. nginx can't be kill -9ed, it needs a reboot.
>
> Has this sort of issue been fixed since 2.6.32?
It would help to see df output for space and inodes of the XFS
filesystem in question.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-09-02 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 12:23 nginx blocked task when XFS partition is very full Sean Purdy
2011-09-02 13:02 ` Stan Hoeppner [this message]
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=4E60D3CD.5030806@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.com \
/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