Rick,
That's something of a time bomb - If one of those directories fsck
wishes it could correct is small and grows in number of files, you'll
get the MDT going read only (and a few odd LBUGs if you try to put it back).
- Patrick
On 10/27/2015 12:18 PM, Mohr Jr, Richard Frank (Rick Mohr) wrote:
On Oct 27, 2015, at 11:22 AM, Chris Hunter <chris.hun...@yale.edu> wrote:
We have a lustre 1.8 filesystem that was upgraded to lustre 2.x and "dirdata" feature was
enabled. We encountered LU-5626/LU-2638 issue with ".." directory entries. Are there
established recovery steps for this issue ?
If I run fsck, the directory entries will be moved into lost+found.
I assume the next step is to run the ll_recover_lost_found_objs tool ?
Can you share any advice/experience about recovery ?
I only recall seeing the bug once on my file system (about a year after we
upgraded), so it really hasn’t been a problem. It has been a while, so I don’t
remember the details. But I think I just handled it by not letting fsck make
any “corrections”.
--
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
_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
