xfs
[Top] [All Lists]

Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4
From: Chandra Seetharaman <sekharan@xxxxxxxxxx>
Date: Thu, 17 Feb 2011 10:49:10 -0800
Cc: xfs@xxxxxxxxxxx
In-reply-to: <4D5C8F4D.1060804@xxxxxxxxxxx>
Organization: IBM
References: <1297798863.32230.222.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20110215223022.GE13052@dastard> <1297886433.32230.224.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20110216221433.GG13052@dastard> <1297899728.32230.225.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4D5C8F4D.1060804@xxxxxxxxxxx>
Reply-to: sekharan@xxxxxxxxxx
Thanks for that info, Eric.

Now I increased the filesystem size and I see the following failure
--------------------------------
QA output created by 180
file /mnt/xfsScratchMntPt/456 has incorrect size - sync failed
file /mnt/xfsScratchMntPt/525 has incorrect size - sync failed
file /mnt/xfsScratchMntPt/624 has incorrect size - sync failed
---------------------------------

I guess that is not good :)

chandra
On Wed, 2011-02-16 at 21:00 -0600, Eric Sandeen wrote:
> 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@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs


<Prev in Thread] Current Thread [Next in Thread>