[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

numerous errors on newly built md volume



I'm constructing a raid 5 of 3 160gb sata drives. They're connected to a promise sx4 150 card, using the kernel drives (not promise's binary only drivers).

the raid builds fine, as does creation of the ext3 filesystem. however, if i then run e2fsck (with the -f option since the filesystem is brand new) i get thousands of these type of errors:

Inode 15461 has imagic flag set. Clear<y>? no

Inode 15462 is in use, but has dtime set. Fix<y>? no

Inode 15463 is in use, but has dtime set. Fix<y>? no

Inode 15464 is in use, but has dtime set. Fix<y>? no

Inode 15465 is in use, but has dtime set. Fix<y>? no

Inode 15466 is in use, but has dtime set. Fix<y>? no

Inode 15466 has imagic flag set. Clear<y>? no

Inode 15467 is in use, but has dtime set. Fix<y>? no

Inode 15468 is in use, but has dtime set. Fix<y>? no

Inode 15331 has compression flag set on filesystem without compression support. Clear<y>? no

Inode 15331, i_size is 15275251971216207939, should be 0. Fix<y>? no

Inode 15331, i_blocks is 154520075, should be 0. Fix<y>? no

Inode 15333, i_size is 5330692746792616550, should be 0. Fix<y>? no

Inode 15333, i_blocks is 3419793554, should be 0. Fix<y>? no

Inode 15330 has INDEX_FL flag set but is not a directory.
Clear HTree index<y>? no

it appears to be picking up an error on literally every inode. i've tried rebuilding the raid several times, but always the same result. putting filesystems on the drives individually (i.e., non-raid) causes no such problems.

any thoughts on what could be causing this? or what i can do to further troubleshoot?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]