[Lustre-discuss] ll_ost_creat_* goes bersek (100% cpu used - OST disabled)

Adrian Ulrich adrian at blinkenlights.ch
Sat Aug 14 01:28:15 PDT 2010


> - the on-disk structure of the object directory for this OST is corrupted.
>   Run "e2fsck -fp /dev/{ostdev}" on the unmounted OST filesystem.

e2fsck fixed it: The OST is now running since 40 minutes without problems:

e2fsck 1.41.6.sun1 (30-May-2009)
lustre1-OST0005: recovering journal
lustre1-OST0005 has been mounted 72 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 440696867, block 493, offset 0: directory corrupted
Salvage<y>? yes

Directory inode 440696853, block 517, offset 0: directory corrupted
Salvage<y>? yes

Directory inode 440696842, block 560, offset 0: directory corrupted
Salvage<y>? yes

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached inode 17769156
Connect to /lost+found<y>? yes

Inode 17769156 ref count is 2, should be 1.  Fix<y>? yes

Unattached zero-length inode 17883901.  Clear<y>? yes

Pass 5: Checking group summary information

lustre1-OST0005: ***** FILE SYSTEM WAS MODIFIED *****
lustre1-OST0005: 44279/488382464 files (15.4% non-contiguous), 280329314/1953524992 blocks



But shouldn't the journal of ext3/ldiskfs make running e2fsck unnecessary?


Have a nice weekend and thanks a lot for the fast reply!

Regards,
 Adrian





More information about the lustre-discuss mailing list