> On Apr 17, 2019, at 4:32 AM, Fernando Perez <fpe...@icm.csic.es> wrote: > > I tried to run the e2fsck in the mdt three years ago and the logs shows a lot > of this kind of messages: > >> Unattached inode 26977505 >> Connect to /lost+found? yes >> Inode 26977505 ref count is 2, should be 1. Fix? yes > > In fact I think that the e2fsc ran so slow due that all the mdt inodes were > corrected.
You may already be doing this, but just in case, make sure that you are using the latest version of Whamcloud’s e2fsprogs (https://downloads.whamcloud.com/public/e2fsprogs/latest/). -- Rick Mohr Senior HPC System Administrator National Institute for Computational Sciences http://www.nics.tennessee.edu _______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
