From: Mark Tinguely <tinguely@sgi.com>
To: "Michel Verbraak(1st-Setup)" <info@1st-setup.nl>
Cc: xfs@oss.sgi.com
Subject: Re: xfs blocks (blocked for more than 120 seconds)
Date: Mon, 24 Mar 2014 11:12:57 -0500 [thread overview]
Message-ID: <53305989.3000708@sgi.com> (raw)
In-Reply-To: <533035CF.6050807@1st-setup.nl>
On 03/24/14 08:40, Michel Verbraak(1st-Setup) wrote:
> op 24-03-14 14:27, Mark Tinguely schreef:
>> On 03/24/14 04:24, Michel Verbraak(1st-Setup) wrote:
>>> Hi,
>>>
>>> We have a problem with one of our systems which is using XFS but we are
>>> unable to find the problem. Recently we had two moments, Tuesday 4th of
>>> March and Friday the 21st of March, where we had to reboot the system to
>>> get it up and running again.
>>>
>>> What happens:
>>> - The programs handling files on the XFS disc stop working when
>>> creating, deleting or writing files. They do not error they are just
>>> waiting on the command to complete.
>>> - One of our programs, a java application, goes into very high cpu usage
>>> (50%) which normally is at 1%. This could be something in our java
>>> application but it happens at the moment handling files gets stuck.
>>> - A nice restart of the programs does not succeed as wel a kill -9 does
>>> not work.
>>> - Trying to reboot the servers in a normal fashion does not work. As it
>>> is a virtual machine we have to do a shutdown (unplug power) and start
>>> it up again to get it up and running.
>>>
>>> Following details I have for you:
>>>
>>> System OS: Ubuntu 12.04 LTS
>>> Kernel: 3.2.0-37-generic #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013
>>> x86_64 x86_64 x86_64 GNU/Linux
>>> Server: Virtual machine in a VMWare setup.
>>> Disc: 300GB direct attached LUN
>>>
>>> We have an exact clone of this system for our acceptance environment. In
>>> this environment we are unable to reproduce this problem/situation.
>>>
>>> Differences between the two days is that our services on 2014-03-21 were
>>> quit busy with a lot of file changes on the xfs disc and on 2014-03-04
>>> the system was very quiet on the moment the kernel traces appear and the
>>> services get stuck.
>>>
>>> Any help is appreciated.
>>>
>>> Regards Michel Verbraak.
>>
>>
>> Could you set up kdump and take a core dump next time it hangs?
>> There is a couple suspicious items in the syslog entries
>>
>> --Mark.
>>
>> _______________________________________________
>> xfs mailing list
>> xfs@oss.sgi.com
>> http://oss.sgi.com/mailman/listinfo/xfs
> Mark,
>
> We will setup the kdump. Can you elloborate on your suspicions?
>
> Michel.
I am interested in the AGF buffer locks and it would be nice to know who
hold what locks. The flush workers are interesting too. We have seen
process block worker's writes from completing, so looking at what is
running and scheduled would be interesting. So a vmcore would tell a lot.
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-03-24 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 9:24 xfs blocks (blocked for more than 120 seconds) Michel Verbraak(1st-Setup)
2014-03-24 13:27 ` Mark Tinguely
2014-03-24 13:40 ` Michel Verbraak(1st-Setup)
2014-03-24 16:12 ` Mark Tinguely [this message]
2014-03-24 17:36 ` Dave Chinner
2014-03-25 8:59 ` Michel Verbraak(1st-Setup)
2014-03-25 9:39 ` Michel Verbraak(1st-Setup)
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=53305989.3000708@sgi.com \
--to=tinguely@sgi.com \
--cc=info@1st-setup.nl \
--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;
as well as URLs for NNTP newsgroup(s).