From: Christoph Hellwig <hch@infradead.org>
To: John Quigley <jquigley@jquigley.com>
Cc: XFS Development <xfs@oss.sgi.com>
Subject: Re: XFS corruption with power failure
Date: Tue, 1 Sep 2009 14:13:41 -0400 [thread overview]
Message-ID: <20090901181341.GC26071@infradead.org> (raw)
In-Reply-To: <4A9576F0.2060304@jquigley.com>
On Wed, Aug 26, 2009 at 12:54:56PM -0500, John Quigley wrote:
> John Quigley wrote:
>> John Quigley wrote:
>>> 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.
>>
>> The self-contained and reproducible environment can be downloaded from
>> the following location:
>>
>> http://www.jquigley.com/tmp/xfsVM.tar.bz2
>
> Has anyone by chance had an opportunity to utilize this? Any corruption reports?
Looked at it, but it turns virtualbox is a real big pile of junk
including it's own huge kernel module. Qemu/kvm now has support for the
virtualbox disk images and I will give it a try next.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-09-01 18:13 UTC|newest]
Thread overview: 8+ 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
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 [this message]
2009-09-15 15:50 ` John Quigley
2009-09-17 18:35 ` Christoph Hellwig
2009-09-01 19:17 ` 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=20090901181341.GC26071@infradead.org \
--to=hch@infradead.org \
--cc=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