[LU-1006] Test failure on test suite conf-sanity

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.2.0
• Type: Bug
• Priority: Blocker
• Reporter: Maloo
• Assignee: Niu Yawei (Inactive)
• Resolution: Fixed
• Severity: 3

Description

This issue was created by maloo for Peter Jones <[e-mail]>

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/139efa48-410a-11e1-972d-5254004bbbd3.

Comments

[Peter Jones]

Niu

Could you please look into this one?

Thanks

Peter

[Niu Yawei (Inactive)]

The debug log shows

== conf-sanity test 56: check big indexes == 16:39:05 (1326760745)
fat-intel-3vm7: 
fat-intel-3vm7: mkfs.lustre FATAL: Unable to build fs /dev/lvm-MDS/P0 (256)
fat-intel-3vm7: 
fat-intel-3vm7: mkfs.lustre FATAL: mkfs failed 256

   Permanent disk data:
Target:     lustre-MDTffff
Index:      unassigned
Lustre FS:  lustre
Mount type: ldiskfs
Flags:      0x75
              (MDT MGS needs_index first_time update )
Persistent mount opts: errors=remount-ro,iopen_nopriv,user_xattr,acl
Parameters: sys.timeout=20

device size = 29596MB
formatting backing filesystem ldiskfs on /dev/lvm-MDS/P0
	target name  lustre-MDTffff
	4k blocks     10000
	options       -J size=16 -I 512 -i 2048 -q -O dirdata,uninit_bg,dir_nlink,huge_file,flex_bg -E lazy_journal_init -F
mkfs_cmd = mke2fs -j -b 4096 -L lustre-MDTffff -J size=16 -I 512 -i 2048 -q -O dirdata,uninit_bg,dir_nlink,huge_file,flex_bg -E lazy_journal_init -F /dev/lvm-MDS/P0 10000
   
   Journal size too big for filesystem.

The mkfs for mds device failed, I think it should be testing environment problem.

[Niu Yawei (Inactive)]

Hi, Chris

Could you take a look to see why the mkfs for /dev/lvm-MDS/P0 on fat-intel-3vm7 failed? Thanks.

[Niu Yawei (Inactive)]

Looks it's duplicated with LU-544:

We are making filesystem with 16M journal size on a ~39M mds device, why the mds size is so small? Yujian/Chris, could you take a look? Thanks.

[Jian Yu]

Hi Chris,
From the Maloo report, I saw the b1_8 build was http://build.lab.whamcloud.com/job/lustre-b1_8/100, which was Lustre 1.8.6-wc1. LU-544 was fixed after that release.

Since we always test the interop between the latest b1_8 release and 2.x release, could you please update the autotest system to use Lustre 1.8.7-wc1 release build http://newbuild.whamcloud.com/job/lustre-b1_8/150/ ? Thanks!

[Peter Jones]

This is believed to be fixed in 1.8.7. Please reopen if it reoccurs with 1.8.7