From: John Quigley <jquigley@jquigley.com>
To: XFS Development <xfs@oss.sgi.com>
Subject: Re: XFS corruption with power failure
Date: Sun, 23 Aug 2009 13:17:43 -0500 [thread overview]
Message-ID: <4A9187C7.9010206@jquigley.com> (raw)
In-Reply-To: <4A8C1E6E.8020405@jquigley.com>
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
That's a ~550 MB (compressed) image that can be 'imported' directly into the latest VirtualBox. Instructions for setting up the environment (trivial, should take you a mere couple of minutes):
http://www.jquigley.com/tmp/README.txt
The basic concept here is to use the VM as the file server, accessing the XFS file system thereon through the guest OS which acts as the NFS client. Automated reboots are effected with cron and sysrq 'b', so you can just set this up and run it until failure.
Hope this helps lend insight - if there are any questions, please ask. Thanks for your time.
- John Quigley
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-08-23 18:17 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 ` John Quigley [this message]
2009-08-26 17:54 ` XFS corruption with power failure 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
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=4A9187C7.9010206@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