From: John Quigley <jquigley@jquigley.com>
To: XFS Development <xfs@oss.sgi.com>
Subject: Re: XFS corruption with failover
Date: Wed, 19 Aug 2009 10:46:54 -0500 [thread overview]
Message-ID: <4A8C1E6E.8020405@jquigley.com> (raw)
In-Reply-To: <606994882.2142291250648292843.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
Lachlan McIlroy wrote:
> xfs_logprint doesn't find any problems with this log but that doesn't mean
> the kernel doesn't - they use different implementations to read the log. I
> noticed that the active part of the log wraps around the physical end/start
> of the log which reminds of this fix:
Very interesting indeed, thank you /very/ much for looking at this.
> I think the fix made it into 2.6.24.
We're currently using the very latest 2.6.30, unfortunately. We've distilled this into a reproducible environment with a stack of NFS + XFS to a local disk + automated sysrq 'b' reboots. We're working on getting this bundled up into a nice little package as a VirtualBox vm for your consumption. Please tell me if this is not desirable.
Thanks very much again.
John Quigley
jquigley.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-08-19 15:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <990461759.2142271250648177725.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-08-19 2:18 ` XFS corruption with failover Lachlan McIlroy
2009-08-19 15:46 ` John Quigley [this message]
2009-08-23 18:17 ` XFS corruption with power failure John Quigley
2009-08-26 17:54 ` John Quigley
2009-09-01 18:13 ` Christoph Hellwig
2009-09-15 15:50 ` John Quigley
2009-09-17 18:35 ` Christoph Hellwig
2009-09-01 19:17 ` John Quigley
[not found] <1194138654.75921250838215929.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-08-21 7:11 ` XFS corruption with failover Lachlan McIlroy
[not found] <835473717.1935811250214078456.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-08-14 1:43 ` Lachlan McIlroy
[not found] <424153067.1934481250210293891.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-08-14 0:38 ` Lachlan McIlroy
2009-08-14 1:14 ` John Quigley
2009-08-17 18:04 ` John Quigley
2009-08-13 20:17 John Quigley
2009-08-13 21:17 ` Emmanuel Florac
2009-08-13 22:42 ` Felix Blyakher
2009-08-14 0:52 ` John Quigley
2009-08-14 0:50 ` John Quigley
2009-08-13 21:44 ` Felix Blyakher
2009-08-14 0:31 ` Eric Sandeen
2009-08-14 0:58 ` Lachlan McIlroy
2009-08-14 1:35 ` Eric Sandeen
2009-08-14 1:44 ` John Quigley
2009-08-14 1:06 ` John Quigley
2009-08-14 13:21 ` Felix Blyakher
2009-08-14 0:56 ` John Quigley
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=4A8C1E6E.8020405@jquigley.com \
--to=jquigley@jquigley.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