All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jacek Luczak <difrost.kernel@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Eric Sandeen <sandeen@sandeen.net>,
	LKML <linux-kernel@vger.kernel.org>,
	xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [XFS] 2.6.29-rc2: XFS internal error XFS_WANT_CORRUPTED_GOTO
Date: Tue, 20 Jan 2009 07:13:35 -0500	[thread overview]
Message-ID: <20090120121335.GA19182@infradead.org> (raw)
In-Reply-To: <20090120114906.GA12526@infradead.org>

On Tue, Jan 20, 2009 at 06:49:06AM -0500, Christoph Hellwig wrote:
> > > Just curious:  do you have CONFIG_LBD set?
> > > 
> > Hi Christoph,
> > 
> > the answer is:
> > $ grep LBD .config
> > # CONFIG_LBD is not set
> 
> Ok, let me reproduce it without that set..

Ok, on 32-bit x86 without CONFIG_LBD I can reliably reproduce the issue
with the following script:


#!/bin/bash

TESTDIR=/mnt/test
SCRATCHMNT=/mnt/scratch
file=$SCRATCHMNT/f

do_pwrite()
{
	offset=`expr $1 \* 512`
	end=`expr $2 \* 512`
	length=`expr $end - $offset`

	xfs_io -d -f $file -c "pwrite $offset $length" >/dev/null
}


mkfs.xfs \
	-b size=1024 \
	-d file,name=$TESTDIR/fsfile,size=40146592b,agcount=16 \
	-i attr=0 \
	-l version=1

mount -o loop,rw,noatime,nodiratime $TESTDIR/fsfile $SCRATCHMNT

do_pwrite 30792 31039
do_pwrite 30320 30791
do_pwrite 29688 30319
do_pwrite 29536 29687
do_pwrite 27216 29535
do_pwrite 24368 27215
do_pwrite 21616 24367
do_pwrite 20608 21615
do_pwrite 19680 20607
do_pwrite 19232 19679
do_pwrite 17840 19231
do_pwrite 16928 17839
do_pwrite 15168 16927
do_pwrite 14048 15167
do_pwrite 12152 14047
do_pwrite 11344 12151
do_pwrite 8792 11343
do_pwrite 6456 8791
do_pwrite 5000 6455
do_pwrite 1728 4999
do_pwrite 0 1727

sync
sync

> $SCRATCHMNT/bigfile

#umount $SCRATCH

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

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Jacek Luczak <difrost.kernel@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Eric Sandeen <sandeen@sandeen.net>,
	LKML <linux-kernel@vger.kernel.org>,
	xfs mailing list <xfs@oss.sgi.com>,
	Dave Chinner <david@fromorbit.com>
Subject: Re: [XFS] 2.6.29-rc2: XFS internal error XFS_WANT_CORRUPTED_GOTO
Date: Tue, 20 Jan 2009 07:13:35 -0500	[thread overview]
Message-ID: <20090120121335.GA19182@infradead.org> (raw)
In-Reply-To: <20090120114906.GA12526@infradead.org>

On Tue, Jan 20, 2009 at 06:49:06AM -0500, Christoph Hellwig wrote:
> > > Just curious:  do you have CONFIG_LBD set?
> > > 
> > Hi Christoph,
> > 
> > the answer is:
> > $ grep LBD .config
> > # CONFIG_LBD is not set
> 
> Ok, let me reproduce it without that set..

Ok, on 32-bit x86 without CONFIG_LBD I can reliably reproduce the issue
with the following script:


#!/bin/bash

TESTDIR=/mnt/test
SCRATCHMNT=/mnt/scratch
file=$SCRATCHMNT/f

do_pwrite()
{
	offset=`expr $1 \* 512`
	end=`expr $2 \* 512`
	length=`expr $end - $offset`

	xfs_io -d -f $file -c "pwrite $offset $length" >/dev/null
}


mkfs.xfs \
	-b size=1024 \
	-d file,name=$TESTDIR/fsfile,size=40146592b,agcount=16 \
	-i attr=0 \
	-l version=1

mount -o loop,rw,noatime,nodiratime $TESTDIR/fsfile $SCRATCHMNT

do_pwrite 30792 31039
do_pwrite 30320 30791
do_pwrite 29688 30319
do_pwrite 29536 29687
do_pwrite 27216 29535
do_pwrite 24368 27215
do_pwrite 21616 24367
do_pwrite 20608 21615
do_pwrite 19680 20607
do_pwrite 19232 19679
do_pwrite 17840 19231
do_pwrite 16928 17839
do_pwrite 15168 16927
do_pwrite 14048 15167
do_pwrite 12152 14047
do_pwrite 11344 12151
do_pwrite 8792 11343
do_pwrite 6456 8791
do_pwrite 5000 6455
do_pwrite 1728 4999
do_pwrite 0 1727

sync
sync

> $SCRATCHMNT/bigfile

#umount $SCRATCH

  reply	other threads:[~2009-01-20 12:13 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19 11:49 [XFS] 2.6.29-rc2: XFS internal error XFS_WANT_CORRUPTED_GOTO Jacek Luczak
2009-01-19 18:44 ` Eric Sandeen
2009-01-19 18:44   ` Eric Sandeen
2009-01-20  0:46   ` Dave Chinner
2009-01-20  0:46     ` Dave Chinner
2009-01-20  9:26     ` Jacek Luczak
2009-01-20  9:26       ` Jacek Luczak
2009-01-20 11:29     ` Christoph Hellwig
2009-01-20 11:29       ` Christoph Hellwig
2009-01-20 11:47       ` Jacek Luczak
2009-01-20 11:47         ` Jacek Luczak
2009-01-20 11:49         ` Christoph Hellwig
2009-01-20 11:49           ` Christoph Hellwig
2009-01-20 12:13           ` Christoph Hellwig [this message]
2009-01-20 12:13             ` Christoph Hellwig
2009-01-20 12:45             ` Christoph Hellwig
2009-01-20 12:45               ` Christoph Hellwig
2009-01-20 13:58               ` Jacek Luczak
2009-01-20 13:58                 ` Jacek Luczak
2009-01-20 14:05                 ` Christoph Hellwig
2009-01-20 14:05                   ` Christoph Hellwig
2009-01-20 14:13                   ` Jacek Luczak
2009-01-20 14:13                     ` Jacek Luczak
2009-01-20 14:23                   ` Jacek Luczak
2009-01-20 14:23                     ` Jacek Luczak
2009-01-20 14:32                     ` Christoph Hellwig
2009-01-20 14:32                       ` Christoph Hellwig
2009-01-21  4:05                     ` Dave Chinner
2009-01-21  4:05                       ` Dave Chinner
2009-01-21  9:04                       ` Jacek Luczak
2009-01-21  9:04                         ` Jacek Luczak
2009-01-21 22:58                         ` Dave Chinner
2009-01-21 22:58                           ` Dave Chinner
2009-01-20 13:35           ` Dave Chinner
2009-01-20 13:35             ` Dave Chinner
2009-01-20 23:03             ` [PATCH] " Dave Chinner
2009-01-20 23:03               ` Dave Chinner
2009-01-20 23:22               ` Christoph Hellwig
2009-01-20 23:22                 ` Christoph Hellwig
2009-01-20  9:24   ` Jacek Luczak
2009-01-20  9:24     ` Jacek Luczak
2009-01-20 10:42     ` Jacek Luczak
2009-01-20 10:42       ` Jacek Luczak

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=20090120121335.GA19182@infradead.org \
    --to=hch@infradead.org \
    --cc=difrost.kernel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --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.