From: Michael Weissenbacher <mw@dermichi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com
Subject: Re: XFS hang during xfs_fsr run
Date: Fri, 12 Mar 2010 10:45:19 +0100 [thread overview]
Message-ID: <4B9A0D2F.30506@dermichi.com> (raw)
In-Reply-To: <20100311233934.GB4732@dastard>
Hi Dave!
> Hi Michael - have you got any idea what the files are that are
> hitting this? This failure is implying that the inode is still dirty
> after syncing all the data. Is something trying to modify it while
> XFS is trying to map it?
Yes, as far as i can tell it's always a file that some process is
currently modifying. It happens ofter with some file unter /var/log
which syslog is currently modifying. I tried setting the "no-defrag"
flag via xfs_io's chattr on all log files but that didn't seem to help.
It seems that cyrus imapd is triggering this problem far more likely
than any other program. Some examples of files where it usually hangs:
/var/spool/imap/x/user/xxxx/cyrus.cache (lsof -> cyrus)
/var/imap/db/log.xxxxxxx (lsof -> cyrus)
/var/log/xxx.log (lsof -> syslog)
> We've seen this occasionally in the past, but we've never been able
> to reproduce it with any reliability. Hence any information you can
> extract would certainly help us here.
I've also seen this happen occasionally before, but recently it started
to happen on about every second run of xfs_fsr. Because this is a
production system i've ceased using xfs_fsr for the moment. I've not
been able to reproduce it on others systems yet.
cheers,
Michael
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-03-12 9:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 10:10 XFS hang during xfs_fsr run Michael Weissenbacher
2010-03-04 11:20 ` Dave Chinner
2010-03-04 12:08 ` Michael Weissenbacher
2010-03-04 13:15 ` Dave Chinner
2010-03-04 13:46 ` Christoph Hellwig
2010-03-04 14:20 ` Michael Weissenbacher
2010-03-04 14:30 ` Christoph Hellwig
2010-03-04 17:14 ` Michael Weissenbacher
2010-03-04 22:26 ` Dave Chinner
2010-03-05 9:04 ` Michael Weissenbacher
2010-03-06 21:20 ` Michael Weissenbacher
2010-03-08 0:06 ` Dave Chinner
2010-03-08 12:17 ` Michael Weissenbacher
2010-03-08 18:09 ` Eric Sandeen
2010-03-09 9:14 ` Michael Weissenbacher
2010-03-09 11:38 ` Dave Chinner
2010-03-09 12:09 ` Michael Weissenbacher
2010-03-10 8:46 ` Michael Weissenbacher
2010-03-11 23:39 ` Dave Chinner
2010-03-12 9:45 ` Michael Weissenbacher [this message]
2010-03-12 10:00 ` Christoph Hellwig
2010-03-12 10:36 ` Michael Weissenbacher
2010-03-12 11:56 ` Dave Chinner
2010-03-12 14:27 ` Christoph Hellwig
2010-03-13 0:25 ` Dave Chinner
2010-04-16 8:10 ` Michael Monnerie
2010-04-16 10:50 ` Michael Weissenbacher
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=4B9A0D2F.30506@dermichi.com \
--to=mw@dermichi.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=sandeen@sandeen.net \
--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