> the filesystem seems to be a disaster, probably due to bad disks - xfs_repair can't repair bad hardware, of course. > > current xfs_repair completes for me without error, after spitting out over 450,000 lines of detected corruption issues. > > so my suggestions going forward would be: > > 1) fix storage > 2) get newer admin tools for next time > > I appreciate the report, but not much to do w/ such an old version (and it seems already fixed in any case). Since I knew that there were issues with the hardware, that's pretty much what I expected to hear. It's good to know that the current version could repair this sort of problem. Thanks for the reply. Regards, Rich Otero EditShare rotero@xxxxxxxxxxxxx 617-782-0479 On Wed, Jun 26, 2019 at 6:10 PM Eric Sandeen <sandeen@xxxxxxxxxxx> wrote: > > On 6/26/19 4:30 PM, Rich Otero wrote: > >> This applies > >> http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F > > > > kernel version: 3.12.17 > > ~6 years old :( > > > xfsprogs version: 3.1.7 > > 8 years old :( So, bug reports are not really useful here ;) > > the filesystem seems to be a disaster, probably due to bad disks - xfs_repair can't repair bad hardware, of course. > > current xfs_repair completes for me without error, after spitting out over 450,000 lines of detected corruption issues. > > so my suggestions going forward would be: > > 1) fix storage > 2) get newer admin tools for next time > > I appreciate the report, but not much to do w/ such an old version (and it seems already fixed in any case). > > -Eric
