From: Lachlan McIlroy <lmcilroy@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: Oops at xfs_bmbt_get_startoff in SLES 10 2.6.16
Date: Thu, 23 Apr 2009 22:43:16 -0400 (EDT) [thread overview]
Message-ID: <144122190.4081240540996189.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <20090423094741.GA23157@infradead.org>
----- "Christoph Hellwig" <hch@infradead.org> wrote:
> Lachlan,
>
> any chance we could get you to resubmit the minimal locking fix for
> now?
Okay, done. If people still see problems then we should take the
rest of the patch too (of course I would suggest taking it anyway
but it needs more soak testing).
>
> We can play with the test program than to find some cause the other
I suggest increasing or decreasing the -l argument until you can
reproduce the problem. Timing it so that the file's data is being
flushed to disk (and therefore delayed allocations being converted
and extents merged) at the same time the file is closed (ie the
fput() is done) can be tricky.
It may be easier to reproduce if another program, running concurrently
to the test program, is simply opening and close the file repeatedly.
> corruptions. We also still have that non-freed attr fork patch that
> was
> somewhat related which we still need get done :P
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2009-04-24 2:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1416563271.242851240369384712.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-04-22 3:06 ` Oops at xfs_bmbt_get_startoff in SLES 10 2.6.16 Lachlan McIlroy
2009-04-23 9:47 ` Christoph Hellwig
2009-04-24 2:43 ` Lachlan McIlroy [this message]
2009-03-12 18:50 Kevin Jamieson
2009-03-12 19:23 ` Eric Sandeen
2009-03-12 23:13 ` Kevin Jamieson
2009-04-22 0:54 ` Kevin Jamieson
2009-04-22 2:16 ` Eric Sandeen
2009-04-22 2:31 ` Felix Blyakher
2009-04-22 2:32 ` Eric Sandeen
2009-04-22 2:35 ` Felix Blyakher
2009-04-22 2:38 ` Eric Sandeen
2009-04-23 6:24 ` Kevin Jamieson
2009-04-23 6:18 ` Kevin Jamieson
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=144122190.4081240540996189.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com \
--to=lmcilroy@redhat.com \
--cc=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox