Details
-
Bug
-
Resolution: Cannot Reproduce
-
Blocker
-
None
-
Lustre 2.4.0
-
None
-
3
-
5323
Description
This issue was created by maloo for sarah <sarah@whamcloud.com>
This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/7031f4e6-21c3-11e2-b552-52540035b04c.
The sub-test lfsck failed with the following error:
test failed to respond and timed out
I think this is related to ORI-771
some e2fsck errors in suite_log:
e2fsck -d -v -t -t -f -n --mdsdb /home/autotest/.autotest/shared_dir/2012-09-07/232903-7fbcd335b690/mdsdb --ostdb /home/autotest/.autotest/shared_dir/2012-09-07/232903-7fbcd335b690/ostdb-5 /dev/dm-5 CMD: client-14vm4 e2fsck -d -v -t -t -f -n --mdsdb /home/autotest/.autotest/shared_dir/2012-09-07/232903-7fbcd335b690/mdsdb --ostdb /home/autotest/.autotest/shared_dir/2012-09-07/232903-7fbcd335b690/ostdb-5 /dev/dm-5 client-14vm4: e2fsck 1.42.3.wc3 (15-Aug-2012) client-14vm4: [ERROR] mkquota.c:427:scan_dquots_callback:: Usage inconsistent for ID 0: (1507328, 1030) != (36864, 4) client-14vm4: [ERROR] mkquota.c:427:scan_dquots_callback:: Usage inconsistent for ID 0: (1507328, 1030) != (36864, 4) Warning! /dev/dm-5 is in use. Warning: skipping journal recovery because doing a read-only filesystem check. Pass 1: Checking inodes, blocks, and sizes Pass 1: Memory used: 272k/0k (163k/110k), time: 0.15/ 0.03/ 0.02 Pass 1: I/O read: 9MB, write: 0MB, rate: 59.64MB/s Pass 2: Checking directory structure Pass 2: Memory used: 448k/0k (220k/229k), time: 0.01/ 0.00/ 0.00 Pass 2: I/O read: 1MB, write: 0MB, rate: 71.18MB/s Pass 3: Checking directory connectivity Peak memory: Memory used: 448k/0k (220k/229k), time: 0.20/ 0.04/ 0.02 Pass 3: Memory used: 448k/0k (219k/230k), time: 0.00/ 0.00/ 0.00 Pass 3: I/O read: 1MB, write: 0MB, rate: 11235.95MB/s Pass 4: Checking reference counts Pass 4: Memory used: 368k/0k (73k/296k), time: 0.02/ 0.02/ 0.00 Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s Pass 5: Checking group summary information Free blocks count wrong (1699491, counted=1699132). Fix? no Free inodes count wrong (452467, counted=451441). Fix? no