Skip to contentSkip to conversation

xfs_force_shutdown() called when running xfstests on 2.6.38-rc4

PATCH In review Chandra Seetharaman 4 participants 14 messages Feb 15, 2011 – Feb 21, 2011

lore
Share & tools
lore

Chandra Seetharaman

author
#0 lore raw

Hello,

I am running xfstests on a POWER system with 2.6.38-rc4.

I see the following in some of the tests.
-------------------------

Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: xfs_force_shutdown(sdb1,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd000000001505c00
Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: XFS mounting filesystem sdb1
Feb 15 07:16:23 test2 kernel: Starting XFS recovery on filesystem: sdb1 (logdev: internal)
Feb 15 07:16:23 test2 kernel: Ending XFS recovery on filesystem: sdb1 (logdev: internal)

-----------------------

Is it ok ?
needs to be debugged ?
configuration issues ?

chandra

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#1 lore raw
Quoted 14 lines · Chandra Seetharaman

Hello,

I am running xfstests on a POWER system with 2.6.38-rc4.

I see the following in some of the tests.
-------------------------

Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: xfs_force_shutdown(sdb1,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd000000001505c00
Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: XFS mounting filesystem sdb1
Feb 15 07:16:23 test2 kernel: Starting XFS recovery on filesystem: sdb1 (logdev: internal)
Feb 15 07:16:23 test2 kernel: Ending XFS recovery on filesystem: sdb1 (logdev: internal)
Quoted 4 lines

-----------------------

Is it ok ?
needs to be debugged ?

Depends on the test. Some tests initiate a forced shutdown on the filesystem to test certain functionality....

Quoted 1 line

configuration issues ?

No.

Cheers,

Dave.

Signature · 7 lines
Dave Chinner
[email protected]

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
author
#2 lore raw

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

----------------------------

Quoted 23 lines · Dave Chinner
Quoted 14 lines · Chandra Seetharaman

Hello,

I am running xfstests on a POWER system with 2.6.38-rc4.

I see the following in some of the tests.
-------------------------

Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: xfs_force_shutdown(sdb1,0x1) called from line 1111 of file fs/xfs/linux-2.6/xfs_buf.c.  Return address = 0xd000000001505c00
Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: Filesystem sdb1: xfs_log_force: error 5 returned.
Feb 15 07:16:23 test2 kernel: XFS mounting filesystem sdb1
Feb 15 07:16:23 test2 kernel: Starting XFS recovery on filesystem: sdb1 (logdev: internal)
Feb 15 07:16:23 test2 kernel: Ending XFS recovery on filesystem: sdb1 (logdev: internal)
Quoted 4 lines

-----------------------

Is it ok ?
needs to be debugged ?

Depends on the test. Some tests initiate a forced shutdown on the filesystem to test certain functionality....

Quoted 7 lines
Quoted 1 line

configuration issues ?

No.

Cheers,

Dave.

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#3 lore raw
Quoted 36 lines · Chandra Seetharaman

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
Quoted 1 line

----------------------------

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.

Signature · 7 lines
Dave Chinner
[email protected]

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
#4 lore raw

PATCH 1/1 xfstests: Notify via syslog when godown is shutting down fs

Just a hint for those perusing logs that the ensuing shutdown is intentional...

Feb 16 17:06:17 hostname godown: xfstests-induced forced shutdown of /mnt/scratch
Feb 16 17:06:17 hostname kernel: Filesystem "sdb3": xfs_log_force: error 5 returned.
Signed-off-by Eric Sandeen <[email protected]>

---

src/godown.c +3 -0
index 07b6980..b140a41 100644
@@ -16,6 +16,7 @@
  * Inc.,  51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
  */
 
+#include <syslog.h>
 #include "global.h"
 
 static char *xprogname;

@@ -109,6 +110,8 @@ main(int argc, char *argv[])
 	if (verbose_opt) {
 		printf("Calling XFS_IOC_GOINGDOWN\n");
 	}
+	syslog(LOG_WARNING, "xfstests-induced forced shutdown of %s:\n",
+		mnt_dir);
 	if ((xfsctl(mnt_dir, fd, XFS_IOC_GOINGDOWN, &flag)) == -1) {
 		fprintf(stderr, "%s: error on xfsctl(GOINGDOWN) of \"%s\": %s\n",
 			xprogname, mnt_dir, strerror(errno));

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

author
#5 lore raw

Re: [PATCH] xfstests: Notify via syslog when godown is shutting down fs

Thanks Eric. This makes it clear that it is intentional.

chandra

Quoted 31 lines · Eric Sandeen

Just a hint for those perusing logs that the ensuing shutdown is intentional...

Feb 16 17:06:17 hostname godown: xfstests-induced forced shutdown of /mnt/scratch
Feb 16 17:06:17 hostname kernel: Filesystem "sdb3": xfs_log_force: error 5 returned.
Signed-off-by Eric Sandeen <[email protected]>

---

src/godown.c +3 -0
index 07b6980..b140a41 100644
@@ -16,6 +16,7 @@
  * Inc.,  51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
  */
 
+#include <syslog.h>
 #include "global.h"
 
 static char *xprogname;

@@ -109,6 +110,8 @@ main(int argc, char *argv[])
 	if (verbose_opt) {
 		printf("Calling XFS_IOC_GOINGDOWN\n");
 	}
+	syslog(LOG_WARNING, "xfstests-induced forced shutdown of %s:\n",
+		mnt_dir);
 	if ((xfsctl(mnt_dir, fd, XFS_IOC_GOINGDOWN, &flag)) == -1) {
 		fprintf(stderr, "%s: error on xfsctl(GOINGDOWN) of \"%s\": %s\n",
 			xprogname, mnt_dir, strerror(errno));
Quoted 4 lines

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#6 lore raw

Re: [PATCH] xfstests: Notify via syslog when godown is shutting down fs

In reply to Eric Sandeen
Quoted 2 lines · Eric Sandeen

Just a hint for those perusing logs that the ensuing shutdown is intentional...

Good idea.

Signed-off-by Alex Elder <[email protected]>
Quoted 5 lines
Feb 16 17:06:17 hostname godown: xfstests-induced forced shutdown of /mnt/scratch
Feb 16 17:06:17 hostname kernel: Filesystem "sdb3": xfs_log_force: error 5 returned.
Signed-off-by Eric Sandeen <[email protected]>

---

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

author
#7 lore raw
In reply to Dave Chinner

Thanks for the response Dave.

That matches exactly, except for test 180.

chandra

Quoted 58 lines · Dave Chinner
Quoted 36 lines · Chandra Seetharaman

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
Quoted 1 line

----------------------------

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
Quoted 3 lines

Cheers,

Dave.

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#8 lore raw
Quoted 3 lines · Chandra Seetharaman

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

Quoted 63 lines

chandra

Quoted 61 lines · Dave Chinner
Quoted 36 lines · Chandra Seetharaman

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
Quoted 1 line

----------------------------

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
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

author
#9 lore raw

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

Quoted 73 lines · Eric Sandeen
Quoted 3 lines · Chandra Seetharaman

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

Quoted 60 lines

chandra

Quoted 58 lines · Dave Chinner
Quoted 36 lines · Chandra Seetharaman

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
Quoted 1 line

----------------------------

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
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines

Cheers,

Dave.

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#10 lore raw
Quoted 11 lines · Chandra Seetharaman

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 :)

No, not good. It passes here on x86_64 and a couple of different configurations storage back ends (1/2p on h/w raid1 writing @~90MB/s, 8p + s/w RAID0 @ ~700MB/s), so it doesn't seem like there is a generic problem.

what is the hardware you are testing on? Does it happen on every run? What is the size of the files that had incorrect sizes? what is their extent layout?

Cheers,

Dave.

Signature · 7 lines
Dave Chinner
[email protected]

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
author
#11 lore raw
Quoted 11 lines · Dave Chinner
Quoted 10 lines · Chandra Seetharaman

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
---------------------------------

Quoted 8 lines
Quoted 1 line

I guess that is not good :)

No, not good. It passes here on x86_64 and a couple of different configurations storage back ends (1/2p on h/w raid1 writing @~90MB/s, 8p + s/w RAID0 @ ~700MB/s), so it doesn't seem like there is a generic problem.

what is the hardware you are testing on?

PPC64

Quoted 1 line

Does it happen on every run?

No, it is not consistent. It happened as this

+file /mnt/xfsScratchMntPt/993 has incorrect size - sync failed

and ran 10+ times, didn't fail at all.

Quoted 2 lines

What is the size of the files that had incorrect sizes? what is their extent layout?

I will run more times and when they fail get the details.

Quoted 4 lines

Cheers,

Dave.

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#12 lore raw
Quoted 14 lines · Chandra Seetharaman
Quoted 13 lines · Dave Chinner
Quoted 11 lines · Chandra Seetharaman

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 :)

Quoted 7 lines
Quoted 6 lines

No, not good. It passes here on x86_64 and a couple of different configurations storage back ends (1/2p on h/w raid1 writing @~90MB/s, 8p + s/w RAID0 @ ~700MB/s), so it doesn't seem like there is a generic problem.

what is the hardware you are testing on?

PPC64

Yes, I know you are running on PPC64, but that doesn't tell me anything about the hardware you are running on. How many CPUs, how much RAM, what storage you are using, how it is configured, etc, is the sort of infomration relevant to understanding the circumstances around the failures you are seeing...

Quoted 7 lines
Quoted 1 line

Does it happen on every run?

No, it is not consistent. It happened as this

+file /mnt/xfsScratchMntPt/993 has incorrect size - sync failed

and ran 10+ times, didn't fail at all.

OK. So it's a relatively rare failure, then?

Cheers,

Dave.

Signature · 7 lines
Dave Chinner
[email protected]

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
author
#13 lore raw
Quoted 20 lines · Dave Chinner
Quoted 19 lines · Chandra Seetharaman
Quoted 18 lines · Dave Chinner
Quoted 11 lines · Chandra Seetharaman

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 :)

No, not good. It passes here on x86_64 and a couple of different configurations storage back ends (1/2p on h/w raid1 writing @~90MB/s, 8p + s/w RAID0 @ ~700MB/s), so it doesn't seem like there is a generic problem.

Quoted 4 lines
Quoted 2 lines
Quoted 1 line

what is the hardware you are testing on?

PPC64

Yes, I know you are running on PPC64, but that doesn't tell me

It is a 4 processor quad-core, which gets 16 procs. 32G RAM.

Storage is a ipr RAID0 of 2 500G sas disks.

Filesystem size is 20G.

Quoted 7 lines

anything about the hardware you are running on. How many CPUs, how much RAM, what storage you are using, how it is configured, etc, is the sort of infomration relevant to understanding the circumstances around the failures you are seeing...

Quoted 2 lines
Quoted 1 line

Does it happen on every run?

Quoted 7 lines
Quoted 5 lines

No, it is not consistent. It happened as this

+file /mnt/xfsScratchMntPt/993 has incorrect size - sync failed

and ran 10+ times, didn't fail at all.

OK. So it's a relatively rare failure, then?

Very rare. I ran it more than 20 times yesterday night, and it didn't fail.

chandra

Quoted 4 lines

Cheers,

Dave.

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs