From: John Quigley <jquigley@jquigley.com>
To: XFS Development <xfs@oss.sgi.com>
Subject: XFS corruption with failover
Date: Thu, 13 Aug 2009 15:17:22 -0500 [thread overview]
Message-ID: <4A8474D2.7050508@jquigley.com> (raw)
Folks:
We're deploying XFS in a configuration where the file system is being exported with NFS. XFS is being mounted on Linux, with default options; an iSCSI volume is the formatted media. We're working out a failover solution for this deployment utilizing Linux HA. Things appear to work correctly in the general case, but in continuous testing we're getting XFS superblock corruption on a very reproducible basis.
The sequence of events in our test scenario:
1. NFS server #1 online
2. Run IO to NFS server #1 from NFS client
3. NFS server #1 offline, (via passing 'b' to /proc/sysrq-trigger)
4. NFS server #2 online
5. XFS mounted as part of failover mechanism, mount fails
The mount fails with the following:
<snip>
kernel: XFS mounting filesystem sde
kernel: Starting XFS recovery on filesystem: sde (logdev: internal)
kernel: XFS: xlog_recover_process_data: bad clientid
kernel: XFS: log mount/recovery failed: error 5
kernel: XFS: log mount failed
</snip>
When running xfs_repair:
<snip>
[root@machine ~]# xfs_repair /dev/sde
xfs_repair: warning - cannot set blocksize on block device /dev/sde: Invalid argument
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs ...
</snip>
Any advice or insight into what we're doing wrong would be very much appreciated. My apologies in advance for the somewhat off-topic question.
- John Quigley
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-08-13 20:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 20:17 John Quigley [this message]
2009-08-13 21:17 ` XFS corruption with failover 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
[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=4A8474D2.7050508@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.