public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: CAI Qian <caiqian@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: stable@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 3.9.3: Oops running xfstests
Date: Thu, 30 May 2013 01:40:32 -0400 (EDT)	[thread overview]
Message-ID: <1824023060.8558101.1369892432333.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20130530052049.GK29466@dastard>



----- Original Message -----
> From: "Dave Chinner" <david@fromorbit.com>
> To: "CAI Qian" <caiqian@redhat.com>
> Cc: xfs@oss.sgi.com, stable@vger.kernel.org
> Sent: Thursday, May 30, 2013 1:20:49 PM
> Subject: Re: 3.9.3: Oops running xfstests
> 
> 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?
I have been running the following workloads, trinity, ltp (including
oom tests and some filesystem tests), some hugetlbfs tests, selinux
test suite, tracepoint tests, connectathon tests and then xfstests.
I am still trying to narrow down the minimal workload that could
reproduce this.
> 
> <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?
+ export TEST_DEV=/dev/mapper/rhel_hp--bl495cg5--02-swap
+ TEST_DEV=/dev/mapper/rhel_hp--bl495cg5--02-swap
+ export TEST_DIR=/mnt/testarea/test
+ TEST_DIR=/mnt/testarea/test
+ export SCRATCH_DEV=/dev/mapper/rhel_hp--bl495cg5--02-home
+ SCRATCH_DEV=/dev/mapper/rhel_hp--bl495cg5--02-home
+ export SCRATCH_MNT=/mnt/testarea/scratch
+ SCRATCH_MNT=/mnt/testarea/scratch
+ mkdir -p /mnt/testarea/test
home = /dev/mapper/rhel_hp--bl495cg5--02-home
+ mkdir -p /mnt/testarea/scratch
+ mkfs.xfs -f /dev/mapper/rhel_hp--bl495cg5--02-swap
meta-data=/dev/mapper/rhel_hp--bl495cg5--02-swap isize=256    agcount=4, agsize=510976 blks
         =                       sectsz=512   attr=2, projid32bit=0
data     =                       bsize=4096   blocks=2043904, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
+ mkfs.xfs -f /dev/mapper/rhel_hp--bl495cg5--02-home
meta-data=/dev/mapper/rhel_hp--bl495cg5--02-home isize=256    agcount=4, agsize=1103872 blks
         =                       sectsz=512   attr=2, projid32bit=0
data     =                       bsize=4096   blocks=4415488, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
> 
> And can you post the xfs_info output of the filesystems under test,
> too?
xfs_info: /dev/mapper/rhel_hp--bl495cg5--02-swap is not a mounted XFS filesystem
+ echo

+ xfs_info /dev/mapper/rhel_hp--bl495cg5--02-home
meta-data=/dev/mapper/rhel_hp--bl495cg5--02-home isize=256    agcount=4, agsize=1103872 blks
         =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=4415488, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal               bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
CAI Qian
> 
> 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:40 UTC|newest]

Thread overview: 18+ 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
2013-05-30  5:40             ` CAI Qian [this message]
2013-05-31  3:03               ` 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests) CAI Qian
2013-05-31  5:35                 ` Eric Sandeen
2013-05-31  6:04                 ` Dave Chinner
2013-06-03  3:04                   ` CAI Qian
2013-06-03  4:00                     ` Dave Chinner
2013-06-04  3:14                       ` CAI Qian
2013-06-04  4:16                         ` Dave Chinner
2013-06-04  4:29                           ` Dave Chinner
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=1824023060.8558101.1369892432333.JavaMail.root@redhat.com \
    --to=caiqian@redhat.com \
    --cc=david@fromorbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox