From: John Quigley <jquigley@jquigley.com>
Cc: XFS Development <xfs@oss.sgi.com>
Subject: Re: XFS corruption with failover
Date: Thu, 13 Aug 2009 19:56:09 -0500 [thread overview]
Message-ID: <4A84B629.3080208@jquigley.com> (raw)
In-Reply-To: <E037F1E5-2CC8-4F6E-92ED-AFE7BE6EBD1B@sgi.com>
Felix Blyakher wrote:
> This is an IO error. Is the block device (/dev/sde) accessible
> from the server #2 OK? Can you dd from that device?
Interesting suggestion; I don't recall having seen any indication of IO errors, but I'm testing again this evening, and will report back on what I find with dd.
> That's not a good time to run xfs_repair. There were no
> indication that the filesystem is corrupted.
Interesting again. I ran the tool merely because I had no other recourse to remedy this.
> Let's take for a sec "NFS server #2" out of the picture.
> Can you mount the filesystem from the original server
> after it reboots?
This has been tested and fails, so it does appear to be a corruption issue on the stable media. Based on your first comment, I'm re-running tests to verify that the ISCSI volumes are fully online and ready to accept IO before mounting the file system.
Thank you very much.
- John Quigley
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-08-14 0:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 20:17 XFS corruption with failover 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 [this message]
[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
[not found] <835473717.1935811250214078456.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-08-14 1:43 ` Lachlan McIlroy
[not found] <990461759.2142271250648177725.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-08-19 2:18 ` Lachlan McIlroy
2009-08-19 15:46 ` John Quigley
[not found] <1194138654.75921250838215929.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-08-21 7:11 ` Lachlan McIlroy
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=4A84B629.3080208@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