Is it normal for e2fsck running on an MDT with --msdb to take over a week? The entire MDT is only 500GB. So far it has only output: e2fsck 1.42.7.wc2 (07-Nov-2013) WORK=MDT0000 lustre database creation, check forced. Pass 1: Checking inodes, blocks, and sizes MDS: ost_idx 0 max_id 6351370 MDS: ost_idx 1 max_id 5766664 MDS: ost_idx 2 max_id 5821326 MDS: ost_idx 3 max_id 5720490 MDS: ost_idx 4 max_id 2889092 MDS: ost_idx 5 max_id 2654116 MDS: ost_idx 6 max_id 2805220 MDS: ost_idx 7 max_id 2895847 MDS: ost_idx 8 max_id 2932156 MDS: ost_idx 9 max_id 2777382 MDS: ost_idx 10 max_id 2764932 MDS: ost_idx 11 max_id 2655203 MDS: ost_idx 12 max_id 2742542 MDS: ost_idx 13 max_id 2856457 MDS: got 112 bytes = 14 entries in lov_objids MDS: max_files = 32837426 MDS: num_osts = 14 mds info db file written Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Pass 6: Acquiring MDT information for lfsck Brian Andrus ITACS/Research Computing Naval Postgraduate School Monterey, California voice: 831-656-6238 _______________________________________________ Lustre-discuss mailing list Lustre-discuss-aLEFhgZF4x6X6Mz3xDxJMA@public.gmane.org http://lists.lustre.org/mailman/listinfo/lustre-discuss