[LU-2471] conf-sanity test_24a: mkfs.lustre FATAL: unable to prepare backend Created: 11/Dec/12 Updated: 27/Aug/19 Resolved: 22/Dec/12 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.4.0 |
| Fix Version/s: | Lustre 2.4.0 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Maloo | Assignee: | Li Wei (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | HB | ||
| Environment: |
lustre master build #1104 with ZFS |
||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 5817 | ||||||||
| 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/70b27b00-4295-11e2-8dba-52540035b04c. The sub-test test_24a failed with the following error:
CMD: client-29vm3 mkfs.lustre --mgsnode=client-29vm3@tcp --fsname=lustre --mdt --index=0 --param=sys.timeout=20 --param=lov.stripesize=1048576 --param=lov.stripecount=0 --param=mdt.identity_upcall=/usr/sbin/l_getidentity --backfstype=ldiskfs --device-size=2097152 --mkfsoptions=\"-E lazy_itable_init\" --mountfsoptions=errors=remount-ro,iopen_nopriv,user_xattr,acl --nomgs --mgsnode=client-29vm3@tcp --fsname=test1234 --reformat lustre-mdt1_2/mdt1_2 /dev/lvm-MDS/S1 |
| Comments |
| Comment by Li Wei (Inactive) [ 18/Dec/12 ] |
|
The format command Sarah quoted is indeed inconsistent: ... --backfstype=ldiskfs ... lustre-mdt1_2/mdt1_2 /dev/lvm-MDS/S1 According the "lustre-initialisation" log in the Maloo session, Autotest gave these: 06:51:51:export MDSFSTYPE=ldiskfs 06:51:51:export MGSFSTYPE=zfs ... 06:51:51:export OSTFSTYPE=zfs 06:51:52:export FSTYPE=zfs Thus, "--backfstype=ldiskfs" was correct, while mdsdevname() and mdsvdevname() generated incorrect device names. There are two issues need to be fixed here:
I'll submit patch for issue 2. |
| Comment by Li Wei (Inactive) [ 18/Dec/12 ] |
| Comment by Li Wei (Inactive) [ 22/Dec/12 ] |
|
The patch has landed to master. The Autotest issue has been reported to Chris and, I believe, has been fixed in Autotest configurations. |