On 11/21/22 10:14 AM, Carlos Maiolino wrote: > Hi. > > > On Sat, Nov 19, 2022 at 12:24:18PM -0500, iamdooser wrote: >> Thank you for responding. >> >> Yes that found errors, although I'm not accustomed to interpreting the >> output. >> >> xfs_repair version 5.18.0 >> >> The output of xfs_repair -nv was quite large, as was the >> xfs_metadump...not sure that's indicative of something, but I've >> uploaded them here: >> https://drive.google.com/drive/folders/1OyQOZNsTS1w1Utx1ZfQEH-bS_Cyj8-F2?usp=sharing >> >> >> There doesn't seem to be much activity once it hangs at "process newly >> discovered inodes..." so it doesn't seem like just a slow repair. >> Desipte there being no sign of activity, I've let it run for 24+ hours >> and saw no changes.. >> > > Before anything else, could you please try to run the latest xfsprogs from: > > https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/log/?h=master > > A quick test in my laptop using the metadump you provided, finished the repair > in about 5 mintues: > > Maximum metadata LSN (2138201505:-135558109) is ahead of log (96:0). > Format log to cycle 2138201508. > > XFS_REPAIR Summary Mon Nov 21 17:04:44 2022 > > Phase Start End Duration > Phase 1: 11/21 16:59:36 11/21 16:59:36 > Phase 2: 11/21 16:59:36 11/21 16:59:37 1 second > Phase 3: 11/21 16:59:37 11/21 17:03:47 4 minutes, 10 seconds > Phase 4: 11/21 17:03:47 11/21 17:04:06 19 seconds > Phase 5: 11/21 17:04:06 11/21 17:04:07 1 second > Phase 6: 11/21 17:04:07 11/21 17:04:38 31 seconds > Phase 7: 11/21 17:04:38 11/21 17:04:38 > > Total run time: 5 minutes, 2 seconds > done > > Also, feel free to compress any file you need to share with us :) Yup. All those files should compress quite well. So, the "-nv" output shows many, many errors. While xfs_repair should eventually make the filesystem metadata consistent again, that's not the same thing as data recovery. What happened to this filesystem and/or its storage that prompted the need for repair? -Eric
