All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: CAI Qian <caiqian@redhat.com>
Cc: stable@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 3.9.3: Oops running xfstests
Date: Thu, 30 May 2013 15:20:49 +1000	[thread overview]
Message-ID: <20130530052049.GK29466@dastard> (raw)
In-Reply-To: <1588848128.8530921.1369885528565.JavaMail.root@redhat.com>

On Wed, May 29, 2013 at 11:45:28PM -0400, CAI Qian wrote:
> Also reproduced this on 3.9.4 on several different machines.

How? what workload are you running that causes it to occur?

<snip stack trace showing page overrun in
xfs_attr_leaf_compact/xfs_attr_leaf_moveents> 

> System information is below:
> 
> + cat /proc/mounts
....
> /dev/mapper/rhel_hp--xw9400--02-root / xfs rw,seclabel,relatime,attr2,inode64,noquota 0 0
> /dev/mapper/rhel_hp--xw9400--02-home /home xfs rw,seclabel,relatime,attr2,inode64,noquota 0 0
> /dev/sda1 /boot xfs rw,seclabel,relatime,attr2,inode64,noquota 0 0

Which of these filesystems did it happen on? Or some other
filesystem not mounted when you took this snapshot?

And can you post the xfs_info output of the filesystems under test,
too?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2013-05-30  5:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <510292845.4997401.1369279175460.JavaMail.root@redhat.com>
2013-05-23  3:21 ` 3.9.3: Oops running xfstests CAI Qian
2013-05-23  3:51   ` Dave Chinner
2013-05-24  8:52     ` CAI Qian
2013-05-27  5:36       ` Dave Chinner
2013-05-27  6:04         ` CAI Qian
2013-05-28  4:31         ` CAI Qian
2013-05-30  3:45         ` CAI Qian
2013-05-30  5:20           ` Dave Chinner [this message]
2013-05-30  5:40             ` CAI Qian
2013-05-31  3:03               ` 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests) CAI Qian
2013-05-31  3:03                 ` CAI Qian
2013-05-31  3:03                 ` CAI Qian
2013-05-31  5:35                 ` Eric Sandeen
2013-05-31  5:35                   ` Eric Sandeen
2013-05-31  5:35                   ` Eric Sandeen
2013-05-31  6:04                 ` Dave Chinner
2013-05-31  6:04                   ` Dave Chinner
2013-05-31  6:04                   ` Dave Chinner
2013-06-03  3:04                   ` CAI Qian
2013-06-03  3:04                     ` CAI Qian
2013-06-03  3:04                     ` CAI Qian
2013-06-03  4:00                     ` Dave Chinner
2013-06-03  4:00                       ` Dave Chinner
2013-06-03  4:00                       ` Dave Chinner
2013-06-04  3:14                       ` CAI Qian
2013-06-04  3:14                         ` CAI Qian
2013-06-04  3:14                         ` CAI Qian
2013-06-04  4:16                         ` Dave Chinner
2013-06-04  4:16                           ` Dave Chinner
2013-06-04  4:16                           ` Dave Chinner
2013-06-04  4:29                           ` Dave Chinner
2013-06-04  4:29                             ` Dave Chinner
2013-06-04  4:29                             ` Dave Chinner
2013-06-04  4:57                           ` CAI Qian
2013-06-04  4:57                             ` CAI Qian
2013-06-04  4:57                             ` CAI Qian

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=20130530052049.GK29466@dastard \
    --to=david@fromorbit.com \
    --cc=caiqian@redhat.com \
    --cc=stable@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.