On 03/28/2016 04:55 AM, Brian Foster wrote:
On Sat, Mar 26, 2016 at 03:09:27PM -0400, Andrew Ryder wrote:
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
So a read I/O error from the kernel...
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.
... similar read error from xfsprogs...
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
... and it looks like it fails to write as well when trying to zero the
log...
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..
... and this is effectively a repeat of the write error as we try to
format the log with a correct LSN based on the metadata LSN tracked by
the repair process. Your kernel is old enough that runtime probably
won't complain either way (note that 3.19 might be considered a fairly
early kernel for using CRC support). Perhaps the first write attempt
zeroed enough of the log before it failed that log recovery wasn't
required, and thus these problematic I/Os were avoided.
What's the history of this fs? Has it been working for some time, just
recently formatted? What lead to the need for log recovery? What's the
mdadm --detail info, member device size, total array size, xfs_info of
the filesystem, etc..?
Does xfs_repair run clean at this point? If so, does 'xfs_repair -L'
still reproduce the write error (note that I'm assuming you have a clean
log such that this command will not cause data loss). If so, an strace
of the repair process might be interesting...
Brian
The filesystem is about a year old as I had one of the Addonics
backplane boards go bad and after the replacement all was good again..
until the RocketRaid 2722 card and its obscure "Task File error" error
message came up again.
Everything up to this point had been working smoothly since end of Sept
2015 after the rebuild. All disks are 2TB in size, partitioned via
'parted' with 0% and 100% used for partition boundaries on each drive.
Everything had been working wonderfully long before but the array was
taken out due to some issues I had with 3 hitachi drives that refused to
work on the RR2722 card/drivers. Long story.
I've swapped out two drives in the array and no luck yet as it doesn't
seem to be hardware failure related.. I've not had any signs of data
corruption, just meta-data corruption/errors.
If I remember correct, the format applied to the array was done under
3.6.11 kernel as
I'm still going through the same xfs_repair as above to get the array to
mount. It keeps failing after it tries to format the log to cycle 67.
I'll see if I can get you an strace of things.
This all began when the RR2722 driver running under 3.18.15 complained
and ..
Mar 14 07:23:07 Bigmouth kernel: [7177248.090541] /dev/vmnet: port on
hub 0 successfully opened
Mar 14 07:26:03 Bigmouth kernel: [7177424.552323] device eth1 left
promiscuous mode
Mar 14 07:26:03 Bigmouth kernel: [7177424.552786] bridge-eth1: disabled
promiscuous mode
Mar 14 20:10:20 Bigmouth kernel: [7223317.069464] rr272x_1x:Task file
error, StatusReg=0x51, ErrReg=0x84, LBA[0-3]=0x747dc92f,LBA[4-7]=0x0.
Mar 14 20:10:20 Bigmouth kernel: [7223317.179811] sd 5:0:1:0: [sdg]
Mar 14 20:10:21 Bigmouth kernel: [7223317.690439] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 14 20:10:21 Bigmouth kernel: [7223317.700480] sd 5:0:1:0: [sdg] CDB:
Mar 14 20:10:21 Bigmouth kernel: [7223318.211147] Write(10): 2a 00 74 7d
c9 00 00 00 40 00
Mar 14 20:10:21 Bigmouth kernel: [7223318.211167] blk_update_request:
I/O error, dev sdg, sector 1954400512
Mar 14 20:10:21 Bigmouth kernel: [7223318.211203] sd 5:0:3:0: [sdi]
Mar 14 20:10:21 Bigmouth kernel: [7223318.211206] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 14 20:10:21 Bigmouth kernel: [7223318.211209] sd 5:0:3:0: [sdi] CDB:
Mar 14 20:10:21 Bigmouth kernel: [7223318.211211] Write(10): 2a 00 74 7d
c9 00 00 00 40 00
Mar 14 20:10:21 Bigmouth kernel: [7223318.211223] blk_update_request:
I/O error, dev sdi, sector 1954400512
Mar 14 20:10:23 Bigmouth kernel: [7223319.957052] XFS (md2): metadata
I/O error: block 0x15d6d4900 ("xlog_iodone") error 5 numblks 64
Mar 14 20:10:23 Bigmouth kernel: [7223319.957064] XFS (md2):
xfs_do_force_shutdown(0x2) called from line 1181 of file
fs/xfs/xfs_log.c. Return address = 0xffffffff812fdf96
Mar 14 20:10:23 Bigmouth kernel: [7223319.957080] XFS (md2): Log I/O
Error Detected. Shutting down filesystem
Mar 14 20:10:23 Bigmouth kernel: [7223319.957083] XFS (md2): Please
umount the filesystem and rectify the problem(s)
Mar 14 20:10:23 Bigmouth kernel: [7223319.957093] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:10:50 Bigmouth kernel: [7223347.087272] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:11:20 Bigmouth kernel: [7223377.190469] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:11:50 Bigmouth kernel: [7223407.293952] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:12:20 Bigmouth kernel: [7223437.397444] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:12:23 Bigmouth kernel: [7223439.791407] nfsd: last server has
exited, flushing export cache
Mar 14 20:12:50 Bigmouth kernel: [7223467.500928] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:13:20 Bigmouth kernel: [7223497.604420] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:13:50 Bigmouth kernel: [7223527.707899] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:14:21 Bigmouth kernel: [7223557.811399] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:14:51 Bigmouth kernel: [7223587.914932] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:15:21 Bigmouth kernel: [7223618.018362] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:15:51 Bigmouth kernel: [7223648.121779] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:16:19 Bigmouth kernel: [7223676.401069] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:16:21 Bigmouth kernel: [7223678.225334] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:16:27 Bigmouth kernel: [7223684.541305] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:16:27 Bigmouth kernel: [7223684.572176] XFS (md2):
xfs_log_force: error -5 returned.
Mar 14 20:16:38 Bigmouth kernel: [7223694.918565] md2: unknown
partition table
Mar 14 20:16:43 Bigmouth kernel: [7223700.425290] XFS (md2): Mounting V5
Filesystem
Mar 14 20:16:43 Bigmouth kernel: [7223700.545669] XFS (md2): Starting
recovery (logdev: internal)
Mar 14 20:16:44 Bigmouth kernel: [7223701.874245] XFS (md2): Ending
recovery (logdev: internal)
Mar 14 20:30:31 Bigmouth kernel: [7224529.528678] md2: unknown
partition table
/dev/md2:
Version : 1.2
Creation Time : Tue Oct 13 22:21:27 2015
Raid Level : raid5
Array Size : 5860147200 (5588.67 GiB 6000.79 GB)
Used Dev Size : 1953382400 (1862.89 GiB 2000.26 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Tue Apr 12 01:19:43 2016
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Name : Bigmouth:2 (local to host Bigmouth)
UUID : ed979276:3459155c:a32f63da:0c684042
Events : 62846
Number Major Minor RaidDevice State
5 8 193 0 active sync /dev/sdm1
6 8 129 1 active sync /dev/sdi1
2 8 177 2 active sync /dev/sdl1
4 8 113 3 active sync /dev/sdh1
meta-data=/dev/md2 isize=512 agcount=33,
agsize=45782272 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1 spinodes=0
data = bsize=4096 blocks=1465036800, imaxpct=5
= sunit=128 swidth=384 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal bsize=4096 blocks=521728, version=2
= sectsz=512 sunit=8 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
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@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
