public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: sekharan@us.ibm.com
Cc: xfs@oss.sgi.com
Subject: Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4
Date: Wed, 16 Feb 2011 21:00:29 -0600	[thread overview]
Message-ID: <4D5C8F4D.1060804@sandeen.net> (raw)
In-Reply-To: <1297899728.32230.225.camel@chandra-lucid.beaverton.ibm.com>

On 2/16/11 5:42 PM, Chandra Seetharaman wrote:
> Thanks for the response Dave.
> 
> That matches exactly, except for test 180.

180 may not have run due to space requirements:

# Do we have enough space on disk?  10G
_require_fs_space $SCRATCH_MNT 10485760


-Eric

> chandra
> On Thu, 2011-02-17 at 09:14 +1100, Dave Chinner wrote:
>> On Wed, Feb 16, 2011 at 12:00:33PM -0800, Chandra Seetharaman wrote:
>>> Hi Dave,
>>>
>>> These are the failures. Please, let me know if anything need
>>> investigating.
>>>
>>> In some test cases there were more than one, but for simplicity I
>>> removed all but one in this email.
>>>
>>> Thanks
>>>
>>> chandra
>>> -----------------------------------
>>> Feb 16 09:26:04 test35 root: ======== starting XFS test 085 2.6.38-rc4 ========
>>> Feb 16 09:26:06 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> Feb 16 09:26:09 test35 root: ======== starting XFS test 086 2.6.38-rc4 ========
>>> Feb 16 09:26:16 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> Feb 16 09:27:21 test35 root: ======== starting XFS test 087 2.6.38-rc4 ========
>>> Feb 16 09:27:25 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> Feb 16 09:38:38 test35 root: ======== starting XFS test 121 2.6.38-rc4 ========
>>> Feb 16 09:38:46 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> Feb 16 10:33:16 test35 root: ======== starting XFS test 137 2.6.38-rc4 ========
>>> Feb 16 10:33:32 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> Feb 16 10:33:48 test35 root: ======== starting XFS test 138 2.6.38-rc4 ========
>>> Feb 16 10:34:13 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> Feb 16 10:34:45 test35 root: ======== starting XFS test 139 2.6.38-rc4 ========
>>> Feb 16 10:35:12 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> Feb 16 10:35:31 test35 root: ======== starting XFS test 140 2.6.38-rc4 ========
>>> Feb 16 10:35:56 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> Feb 16 10:43:58 test35 root: ======== starting XFS test 179 2.6.38-rc4 ========
>>> Feb 16 10:44:16 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> Feb 16 10:44:36 test35 root: ======== starting XFS test 181 2.6.38-rc4 ========
>>> Feb 16 10:44:49 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> Feb 16 10:44:53 test35 root: ======== starting XFS test 182 2.6.38-rc4 ========
>>> Feb 16 10:44:59 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> Feb 16 10:48:32 test35 root: ======== starting XFS test 200 2.6.38-rc4 ========
>>> Feb 16 10:48:35 test35 kernel: xfs_force_shutdown(sda5,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd0000000098dd3a0
>>> ----------------------------
>>
>> No, they aren't test failures. All these tests trigger a forced
>> shutdown as part of the test, so this is expected output and not an
>> indication of a problem.
>>
>> $ grep -l godown [0-2]*[0-9]
>> 085
>> 086
>> 087
>> 121
>> 137
>> 138
>> 139
>> 140
>> 179
>> 180
>> 181
>> 182
>> 200
>>
>> Cheers,
>>
>> Dave.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-02-17  2:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 19:41 xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 Chandra Seetharaman
2011-02-15 22:30 ` Dave Chinner
2011-02-16 20:00   ` Chandra Seetharaman
2011-02-16 22:14     ` Dave Chinner
2011-02-16 22:53       ` [PATCH] xfstests: Notify via syslog when godown is shutting down fs Eric Sandeen
2011-02-17 17:33         ` Chandra Seetharaman
2011-02-21 23:30         ` Alex Elder
2011-02-16 23:42       ` xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 Chandra Seetharaman
2011-02-17  3:00         ` Eric Sandeen [this message]
2011-02-17 18:49           ` Chandra Seetharaman
2011-02-17 22:52             ` Dave Chinner
2011-02-18  2:09               ` Chandra Seetharaman
2011-02-18  3:30                 ` Dave Chinner
2011-02-18 19:57                   ` Chandra Seetharaman

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=4D5C8F4D.1060804@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=sekharan@us.ibm.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