Re: [lustre-discuss] Stray files after failed lfs_migrate

2021-03-05 Thread Spitz, Cory James via lustre-discuss
> lfsck needs to be done with the whole volume offline? No, in Lustre 2.x lfsck is an online tool. Per https://doc.lustre.org/lustre_manual.xhtml#idm139675950896912: Disaster recovery tool: The Lustre file system provides an online distributed file system check (LFSCK) that can restore consistenc

Re: [lustre-discuss] Stray files after failed lfs_migrate

2021-03-04 Thread Angelos Ching via lustre-discuss
Thanks Rick, I've always assumed those data resides inside MDT, but your explanation makes sense since the files are temporarily files used by mysqld which might have been deleted while the files were being migrated. Since they are not needed anyway, I just unlink-ed them (as rm will stat the

Re: [lustre-discuss] Stray files after failed lfs_migrate

2021-03-03 Thread Mohr, Rick via lustre-discuss
Angelos, If a file still existed on the MDS but its data on the OST had somehow been removed, then you might see symptoms like those you described. (stat fails because info can't be retrieved from the ost, but lfs getstripe can still query layout info from the mds.). But if that is the case,

[lustre-discuss] Stray files after failed lfs_migrate

2021-03-02 Thread Angelos Ching via lustre-discuss
Dear all, I was dealing with some OST migration using lfs_migrate and things went mostly fine albeit for a few files that might have been in use during the migration: # ls ls: cannot access ibleTHWm: No such file or directory ls: cannot access ib7rP0qy: No such file or directory ls: cannot a