| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | XFS corrupt after RAID failure and resync |
| From: | David Raffelt <david.raffelt@xxxxxxxxxxxxx> |
| Date: | Tue, 6 Jan 2015 17:12:14 +1100 |
| Delivered-to: | xfs@xxxxxxxxxxx |
|
Hi again, Some more information.... the kernel log show the following errors were occurring after the RAID recovery, but before I reset the server.Jan 06 00:00:27 server kernel: XFS (md0): Corruption detected. Unmount and run xfs_repair Jan 06 00:00:27ÂserverÂkernel: XFS (md0): Corruption detected. Unmount and run xfs_repair Jan 06 00:00:27ÂserverÂkernel: XFS (md0): Corruption detected. Unmount and run xfs_repair Jan 06 00:00:27ÂserverÂkernel: XFS (md0): metadata I/O error: block 0x36b106c00Â("xfs_trans_read_buf_map") error 117 numblks 16 Jan 06 00:00:27ÂserverÂkernel: XFS (md0): xfs_imap_to_bp: xfs_trans_read_buf() returned error 117. Thanks, Dave |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | XFS corrupt after RAID failure and resync, David Raffelt |
|---|---|
| Next by Date: | Re: What is a recommended XFS sector size for hybrid (512e) advanced format hard drives?, Matthias Schniedermeyer |
| Previous by Thread: | Re: XFS corrupt after RAID failure and resync, Brian Foster |
| Next by Thread: | Re: XFS corrupt after RAID failure and resync, Brian Foster |
| Indexes: | [Date] [Thread] [Top] [All Lists] |