From: Andrew Ryder <tireman@shaw.ca>
To: xfs@oss.sgi.com
Subject: xfs_repair fails after trying to format log cycle?
Date: Sat, 26 Mar 2016 15:09:27 -0400 [thread overview]
Message-ID: <56F6DE67.60403@shaw.ca> (raw)
Hello,
I have an mdadm array with a xfs v5 filesystem on it and its begun to
give me issues when trying to mount it as well as complete xfs_repair.
Not sure if anyone might be able to shed some light on what is going on
or how to correct the issue?
When I try and mount the fs, it complains with:
[ 388.479847] XFS (md2): Mounting V5 Filesystem
[ 388.494686] XFS (md2): metadata I/O error: block 0x15d6d39c0
("xlog_bread_noalign") error 5 numblks 8192
[ 388.495013] XFS (md2): failed to find log head
[ 388.495018] XFS (md2): log mount/recovery failed: error -5
[ 388.495090] XFS (md2): log mount failed
This is where its not making any sense for me, If I try and run
"xfs_repair /dev/md2" it fails with:
Phase 1 - find and verify superblock...
- reporting progress in intervals of 15 minutes
Phase 2 - using internal log
- zero log...
xfs_repair: read failed: Input/output error
failed to find log head
zero_log: cannot find log head/tail (xlog_find_tail=-5)
fatal error -- ERROR: The log head and/or tail cannot be discovered.
Attempt to mount the
filesystem to replay the log or use the -L option to destroy the log and
attempt a repair.
But if I run "xfs_repair -L /dev/md2" which gives:
Phase 1 - find and verify superblock...
- reporting progress in intervals of 15 minutes
Phase 2 - using internal log
- zero log...
xfs_repair: read failed: Input/output error
failed to find log head
zero_log: cannot find log head/tail (xlog_find_tail=-5)
xfs_repair: libxfs_device_zero write failed: Input/output error
then try and re-run "xfs_repair /dev/md2" it starts traversing the
filesystem all the way to "Phase 7" then errors with:
Phase 7 - verify and correct link counts...
- 14:36:55: verify and correct link counts - 33 of 33
allocation groups done
Maximum metadata LSN (64:2230592) is ahead of log (0:0).
Format log to cycle 67.
xfs_repair: libxfs_device_zero write failed: Input/output error
Yet at this point I can now mount the filesystem..
Checking the drives with smartctl shows no errors nor does 'dmesg' show
any hardware i/o or controller related errors...
I've tried scrubbing the array and no bad sectors are found either..
I'm running kernel 3.19.8 with xfsprogs 4.5.
Thanks,
Andrew
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-03-26 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 19:09 Andrew Ryder [this message]
2016-03-28 8:55 ` xfs_repair fails after trying to format log cycle? Brian Foster
2016-04-12 5:53 ` Andrew Ryder
2016-04-12 14:05 ` Brian Foster
2016-04-12 20:16 ` Andrew Ryder
2016-04-13 3:02 ` Andrew Ryder
2016-04-13 4:51 ` Dave Chinner
2016-06-04 2:28 ` Andrew Ryder
2016-06-06 15:33 ` Emmanuel Florac
2016-06-06 19:19 ` Andrew Ryder
2016-06-06 19:37 ` Andrew Ryder
2016-04-13 12:12 ` Brian Foster
2016-04-13 22:34 ` Andrew Ryder
2016-04-14 4:32 ` Andrew Ryder
2016-04-15 4:24 ` Andrew Ryder
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=56F6DE67.60403@shaw.ca \
--to=tireman@shaw.ca \
--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