From: Christoph Hellwig <hch@infradead.org>
To: Mark Tinguely <tinguely@sgi.com>
Cc: Brian Foster <bfoster@redhat.com>, xfs@oss.sgi.com
Subject: Re: XFS: Assertion failed: first <= last && last < BBTOB(bp->b_length), file: fs/xfs/xfs_trans_buf.c, line: 568
Date: Mon, 16 Sep 2013 08:44:23 -0700 [thread overview]
Message-ID: <20130916154423.GA455@infradead.org> (raw)
In-Reply-To: <52325369.1070001@sgi.com>
On Thu, Sep 12, 2013 at 06:51:05PM -0500, Mark Tinguely wrote:
> The secret to tripping over the bug is run the test until fsstress
> fills the filesystem before removing the files. So an error
> handling?
>
> I use the test:
>
> #!/bin/sh
>
> ltp/fsstress -z -s 1378390208 -fsymlink=1 -n9999999 -p4 -d /test2
> cd /test2
> sync
> rm -rf *
>
> If your filesystem is smaller, decrease the -n to make the test faster.
>
> I have still not gotten a core, though Michael Semon sent one.
It would be useful if we could wire this up for xfstests
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-09-16 15:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 18:28 XFS: Assertion failed: first <= last && last < BBTOB(bp->b_length), file: fs/xfs/xfs_trans_buf.c, line: 568 Brian Foster
2013-08-23 13:18 ` Mark Tinguely
2013-08-23 13:30 ` Brian Foster
2013-08-23 13:57 ` Mark Tinguely
2013-08-23 16:49 ` Brian Foster
2013-08-23 18:01 ` Mark Tinguely
2013-08-26 4:13 ` [PATCH] " Dave Chinner
2013-08-26 13:36 ` Brian Foster
2013-08-26 15:00 ` Mark Tinguely
2013-08-26 21:04 ` Dave Chinner
2013-08-26 21:19 ` Mark Tinguely
2013-08-27 13:04 ` Mark Tinguely
2013-08-26 20:26 ` Michael L. Semon
2013-08-29 12:37 ` Mark Tinguely
2013-08-30 14:56 ` Ben Myers
2013-09-12 23:51 ` Mark Tinguely
2013-09-16 15:44 ` Christoph Hellwig [this message]
2013-09-16 17:30 ` Mark Tinguely
2013-09-16 17:41 ` Michael L. Semon
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=20130916154423.GA455@infradead.org \
--to=hch@infradead.org \
--cc=bfoster@redhat.com \
--cc=tinguely@sgi.com \
--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