* xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 @ 2011-02-15 19:41 Chandra Seetharaman 2011-02-15 22:30 ` Dave Chinner 0 siblings, 1 reply; 14+ messages in thread From: Chandra Seetharaman @ 2011-02-15 19:41 UTC (permalink / raw) To: xfs 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 xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 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 0 siblings, 1 reply; 14+ messages in thread From: Dave Chinner @ 2011-02-15 22:30 UTC (permalink / raw) To: Chandra Seetharaman; +Cc: xfs On Tue, Feb 15, 2011 at 11:41:03AM -0800, Chandra Seetharaman wrote: > 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 ? Depends on the test. Some tests initiate a forced shutdown on the filesystem to test certain functionality.... > configuration issues ? No. Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 2011-02-15 22:30 ` Dave Chinner @ 2011-02-16 20:00 ` Chandra Seetharaman 2011-02-16 22:14 ` Dave Chinner 0 siblings, 1 reply; 14+ messages in thread From: Chandra Seetharaman @ 2011-02-16 20:00 UTC (permalink / raw) To: Dave Chinner; +Cc: xfs 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 ---------------------------- On Wed, 2011-02-16 at 09:30 +1100, Dave Chinner wrote: > On Tue, Feb 15, 2011 at 11:41:03AM -0800, Chandra Seetharaman wrote: > > 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 ? > > Depends on the test. Some tests initiate a forced shutdown on the > filesystem to test certain functionality.... > > > configuration issues ? > > No. > > Cheers, > > Dave. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 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-16 23:42 ` xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 Chandra Seetharaman 0 siblings, 2 replies; 14+ messages in thread From: Dave Chinner @ 2011-02-16 22:14 UTC (permalink / raw) To: Chandra Seetharaman; +Cc: xfs 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. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 14+ messages in thread
* [PATCH] xfstests: Notify via syslog when godown is shutting down fs 2011-02-16 22:14 ` Dave Chinner @ 2011-02-16 22:53 ` 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 1 sibling, 2 replies; 14+ messages in thread From: Eric Sandeen @ 2011-02-16 22:53 UTC (permalink / raw) To: Dave Chinner; +Cc: Chandra Seetharaman, xfs 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 <sandeen@redhat.com> --- diff --git a/src/godown.c b/src/godown.c index 07b6980..b140a41 100644 --- a/src/godown.c +++ b/src/godown.c @@ -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 xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply related [flat|nested] 14+ messages in thread
* Re: [PATCH] xfstests: Notify via syslog when godown is shutting down fs 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 1 sibling, 0 replies; 14+ messages in thread From: Chandra Seetharaman @ 2011-02-17 17:33 UTC (permalink / raw) To: Eric Sandeen; +Cc: xfs Thanks Eric. This makes it clear that it is intentional. chandra On Wed, 2011-02-16 at 16:53 -0600, Eric Sandeen wrote: > 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 <sandeen@redhat.com> > --- > > diff --git a/src/godown.c b/src/godown.c > index 07b6980..b140a41 100644 > --- a/src/godown.c > +++ b/src/godown.c > @@ -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 > xfs@oss.sgi.com > http://oss.sgi.com/mailman/listinfo/xfs _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH] xfstests: Notify via syslog when godown is shutting down fs 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 1 sibling, 0 replies; 14+ messages in thread From: Alex Elder @ 2011-02-21 23:30 UTC (permalink / raw) To: Eric Sandeen; +Cc: Chandra Seetharaman, xfs On Wed, 2011-02-16 at 16:53 -0600, Eric Sandeen wrote: > Just a hint for those perusing logs that the ensuing shutdown is > intentional... Good idea. Signed-off-by: Alex Elder <aelder@sgi.com> > 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 <sandeen@redhat.com> > --- _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 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-16 23:42 ` Chandra Seetharaman 2011-02-17 3:00 ` Eric Sandeen 1 sibling, 1 reply; 14+ messages in thread From: Chandra Seetharaman @ 2011-02-16 23:42 UTC (permalink / raw) To: Dave Chinner; +Cc: xfs Thanks for the response Dave. That matches exactly, except for test 180. 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 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 2011-02-17 18:49 ` Chandra Seetharaman 0 siblings, 1 reply; 14+ messages in thread From: Eric Sandeen @ 2011-02-17 3:00 UTC (permalink / raw) To: sekharan; +Cc: xfs 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 2011-02-17 3:00 ` Eric Sandeen @ 2011-02-17 18:49 ` Chandra Seetharaman 2011-02-17 22:52 ` Dave Chinner 0 siblings, 1 reply; 14+ messages in thread From: Chandra Seetharaman @ 2011-02-17 18:49 UTC (permalink / raw) To: Eric Sandeen; +Cc: xfs 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@oss.sgi.com > http://oss.sgi.com/mailman/listinfo/xfs _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 2011-02-17 18:49 ` Chandra Seetharaman @ 2011-02-17 22:52 ` Dave Chinner 2011-02-18 2:09 ` Chandra Seetharaman 0 siblings, 1 reply; 14+ messages in thread From: Dave Chinner @ 2011-02-17 22:52 UTC (permalink / raw) To: Chandra Seetharaman; +Cc: Eric Sandeen, xfs On Thu, Feb 17, 2011 at 10:49:10AM -0800, Chandra Seetharaman wrote: > 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. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 2011-02-17 22:52 ` Dave Chinner @ 2011-02-18 2:09 ` Chandra Seetharaman 2011-02-18 3:30 ` Dave Chinner 0 siblings, 1 reply; 14+ messages in thread From: Chandra Seetharaman @ 2011-02-18 2:09 UTC (permalink / raw) To: Dave Chinner; +Cc: Eric Sandeen, xfs On Fri, 2011-02-18 at 09:52 +1100, Dave Chinner wrote: > On Thu, Feb 17, 2011 at 10:49:10AM -0800, Chandra Seetharaman wrote: > > 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? PPC64 > 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. > 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. > > Cheers, > > Dave. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 2011-02-18 2:09 ` Chandra Seetharaman @ 2011-02-18 3:30 ` Dave Chinner 2011-02-18 19:57 ` Chandra Seetharaman 0 siblings, 1 reply; 14+ messages in thread From: Dave Chinner @ 2011-02-18 3:30 UTC (permalink / raw) To: Chandra Seetharaman; +Cc: Eric Sandeen, xfs On Thu, Feb 17, 2011 at 06:09:40PM -0800, Chandra Seetharaman wrote: > On Fri, 2011-02-18 at 09:52 +1100, Dave Chinner wrote: > > On Thu, Feb 17, 2011 at 10:49:10AM -0800, Chandra Seetharaman wrote: > > > 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? > 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... > > 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. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 2011-02-18 3:30 ` Dave Chinner @ 2011-02-18 19:57 ` Chandra Seetharaman 0 siblings, 0 replies; 14+ messages in thread From: Chandra Seetharaman @ 2011-02-18 19:57 UTC (permalink / raw) To: Dave Chinner; +Cc: Eric Sandeen, xfs On Fri, 2011-02-18 at 14:30 +1100, Dave Chinner wrote: > On Thu, Feb 17, 2011 at 06:09:40PM -0800, Chandra Seetharaman wrote: > > On Fri, 2011-02-18 at 09:52 +1100, Dave Chinner wrote: > > > On Thu, Feb 17, 2011 at 10:49:10AM -0800, Chandra Seetharaman wrote: > > > > 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? > > 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. > 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... > > > > 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? Very rare. I ran it more than 20 times yesterday night, and it didn't fail. chandra > > Cheers, > > Dave. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2011-02-21 23:30 UTC | newest] Thread overview: 14+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox