[LU-1971] lustre-initialization-1: mkfs.lustre FATAL: Loop device setup for /dev/lvm-MDS/P1 failed: Invalid argument Created: 17/Sep/12  Updated: 21/Nov/12  Resolved: 21/Nov/12

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Maloo Assignee: WC Triage
Resolution: Duplicate Votes: 0
Labels: None
Environment:

branch b2_2


Issue Links:
Duplicate
Related
Severity: 3
Rank (Obsolete): 6321

 Description   

This issue was created by maloo for bobijam <bobijam@whamcloud.com>

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/ffaf3af4-0128-11e2-860a-52540035b04c.

16:33:32:Formatting mgs, mds, osts
16:33:32:Format mds1: /dev/lvm-MDS/P1
16:33:32:CMD: client-24vm3 grep -c /mnt/mds1' ' /proc/mounts
16:33:32:CMD: client-24vm3 lsmod | grep lnet > /dev/null && lctl dl | grep ' ST '
16:33:32:CMD: client-24vm3 /usr/sbin/mkfs.lustre --mgs --mdt --fsname=lustre --mountfsoptions=errors=remount-ro,iopen_nopriv,user_xattr,acl --param sys.timeout=20 --device-size=-104857 --backfstype ldiskfs --reformat /dev/lvm-MDS/P1
16:33:32:client-24vm3: mkfs.lustre: Unable to create backing store: 2
16:33:32:client-24vm3: mkfs.lustre: Unable to truncate backing store: 22
16:33:32:client-24vm3:
16:33:32:client-24vm3: mkfs.lustre FATAL: Loop device setup for /dev/lvm-MDS/P1 failed: Invalid argument
16:33:32:
16:33:32: Permanent disk data:
16:33:32:Target: lustre-MDTffff
16:33:32:Index: unassigned
16:33:32:Lustre FS: lustre
16:33:32:Mount type: ldiskfs
16:33:32:Flags: 0x75
16:33:32: (MDT MGS needs_index first_time update )
16:33:32:Persistent mount opts: errors=remount-ro,iopen_nopriv,user_xattr,acl
16:33:32:Parameters: sys.timeout=20
16:33:32:
16:33:32:mkfs.lustre: exiting with 22 (Invalid argument)



 Comments   
Comment by Alex Zhuravlev [ 18/Sep/12 ]

isn't this a duplicate of TT-835 ?

Comment by Andreas Dilger [ 21/Nov/12 ]

Duplicate of TT-835, which was fixed Sept 20, after this ticket was filed.

Generated at Sat Feb 10 01:21:16 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.