From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Greg KH <gregkh@linuxfoundation.org>,
Philipp Herz - Profihost AG <p.herz@profihost.ag>,
stable@vger.kernel.org, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS blocked task in xlog_cil_force_lsn
Date: Tue, 17 Apr 2012 11:19:52 +0200 [thread overview]
Message-ID: <4F8D35B8.4090507@profihost.ag> (raw)
In-Reply-To: <20120417083210.GI6734@dastard>
Am 17.04.2012 10:32, schrieb Dave Chinner:
>>> What's your storage hardware, application, workload, etc?
>> It a Raid 10 of 1TB SATA Drives in front of a 3Ware Controller doing
>> heavy rsync backups.
>
> Hmmm. It sounds like it is just taking a long time for the IO to
> complete, not that there is any other problem. If the IO is realy,
> really slow, the a log force is definitely a place it coul dstall
> for some time.
OK as i've seen this just once it just might be that the controller /
disks were too slow in this case.
> Does the RAID controller have a BBWC?
No but doesn't matter ;-) If it crashes i can just repair the FS and
restart the backup again.
> What IO scheduler are you using?
[root@backup1 ~]# cat /sys/block/sdc/queue/scheduler
[noop] deadline cfq
> Does mounting with nobarriers reduce the stall time?
It is already mounted with nobarrier:
/dev/sdc3 on /sdc3 type xfs (rw,noatime,nodiratime,nobarrier,prjquota)
> Can you reduce the IO load so that it doesn't end up in this state?
Can try that by just doing less backups per time period.
Stefan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-04-17 9:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 6:48 XFS blocked task in xlog_cil_force_lsn Stefan Priebe - Profihost AG
2012-04-16 23:56 ` Dave Chinner
2012-04-17 8:19 ` Stefan Priebe - Profihost AG
2012-04-17 8:32 ` Dave Chinner
2012-04-17 9:19 ` Stefan Priebe - Profihost AG [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-18 2:05 Kevin Richter
2013-12-18 3:38 ` Stan Hoeppner
2013-12-18 10:27 ` Kevin Richter
2013-12-19 14:11 ` Stan Hoeppner
2013-12-20 10:26 ` Kevin Richter
2013-12-20 12:36 ` Stan Hoeppner
2013-12-21 5:30 ` Dave Chinner
2013-12-22 9:18 ` Stan Hoeppner
2013-12-22 20:14 ` Dave Chinner
2013-12-22 21:01 ` Michael L. Semon
2013-12-22 2:35 ` Kevin Richter
2013-12-22 8:12 ` Stan Hoeppner
2013-12-22 14:10 ` Kevin Richter
2013-12-22 17:29 ` Stan Hoeppner
2013-12-20 22:43 ` Arkadiusz Miśkiewicz
2013-12-18 8:33 ` Stefan Ring
2013-12-18 22:21 ` Dave Chinner
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=4F8D35B8.4090507@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=david@fromorbit.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=p.herz@profihost.ag \
--cc=stable@vger.kernel.org \
--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 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.