Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_check\s+segfault\s+\/\s+xfs

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_check\s+segfault\s+\/\s+xfs_repair\s+I\/O\s+error\s*$/: 9 ]

Total 9 documents matching your query.

1. xfs_check segfault / xfs_repair I/O error (score: 1): Author: Drew Wareham <m3rlin@xxxxxxxxx>; Date: Sun, 15 Apr 2012 23:15:09 +1000; Hello Everyone, Hopefully this is the correct kind of information to send to this list. I have an issue with a large XFS volume (17TB) that mounts, but is not readable. I can view the folder structu; /archives/xfs/2012-04/msg00798.html (16,969 bytes)
2. Re: xfs_check segfault / xfs_repair I/O error (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Sun, 15 Apr 2012 14:47:10 -0500; What does an array verify/consistency check say? May be. But I'd exhaust all recovery possibilities before throwing in the towel. You need to identify the root cause of this failure before wiping/rec; /archives/xfs/2012-04/msg00799.html (18,020 bytes)
3. Re: xfs_check segfault / xfs_repair I/O error (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Mon, 16 Apr 2012 08:31:06 +1000; Try upgrading xfsprogs to the latest version first. this is rather old, and the latest versions handle IO errors better... Oh, that's bad. 2 bytes of the magic number are corrupt... And the version i; /archives/xfs/2012-04/msg00800.html (9,910 bytes)
4. Re: xfs_check segfault / xfs_repair I/O error (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Mon, 16 Apr 2012 05:18:53 -0500; https://bugzilla.redhat.com/show_bug.cgi?id=722780 http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/DL180-G5-showing-hard-drive-error-messages/td-p/4771517 http://h30499.www3.hp.com/t5/General/; /archives/xfs/2012-04/msg00816.html (8,423 bytes)
5. Re: xfs_check segfault / xfs_repair I/O error (score: 1): Author: Drew Wareham <m3rlin@xxxxxxxxx>; Date: Fri, 20 Apr 2012 14:11:54 +1000; Hi Dave / Stan, Thanks for taking the time to reply. Unfortunately none of the suggestions were able to recover the data - I'm going to rebuild the array now, but as RAID6 for the extra level of sec; /archives/xfs/2012-04/msg00894.html (12,518 bytes)
6. Re: xfs_check segfault / xfs_repair I/O error (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Fri, 20 Apr 2012 10:06:31 -0500; You reall, Really, REALLY, *REALLY* want to remove kmod-xfs. RHEL5 has been shipping with supported xfs for what, 2 years now, and that old kmod-xfs is an ancient, ancient piece of unmaintained, bitr; /archives/xfs/2012-04/msg00898.html (9,543 bytes)
7. Re: xfs_check segfault / xfs_repair I/O error (score: 1): Author: Drew Wareham <m3rlin@xxxxxxxxx>; Date: Sat, 21 Apr 2012 01:46:17 +1000; Hey Eric, Good point! We're running CentOS 5, so is the CentOS-Plus repo the way to go? These servers are all setup from a fairly old base image hence using kmod-xfs, definitely something I'll addr; /archives/xfs/2012-04/msg00901.html (11,077 bytes)
8. Re: xfs_check segfault / xfs_repair I/O error (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Fri, 20 Apr 2012 12:01:36 -0500; as long as you're on x86_64, the stock kernel has the xfs.ko you want. I'm not big on offering too much centos support, but i would rather not see people using reaaaly crufty xfs. :) -Eric; /archives/xfs/2012-04/msg00902.html (8,721 bytes)
9. Re: xfs_check segfault / xfs_repair I/O error (score: 1): Author: Drew Wareham <m3rlin@xxxxxxxxx>; Date: Sat, 21 Apr 2012 10:57:50 +1000; as long as you're on x86_64, the stock kernel has the xfs.ko you want. I'm not big on offering too much centos support, but i would rather not see people using reaaaly crufty xfs. :) -Eric; /archives/xfs/2012-04/msg00907.html (10,133 bytes)

Current List: 1 - 9
Page: [1]