-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
-
3
-
9223372036854775807
This issue was created by maloo for Andreas Dilger <adilger@dilger.ca>
This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/8e8812f9-3d00-4548-a88b-9a4bfc399e76
lustre-initialization failed with the following error:
LustreError: Can't find device name (need mount option 'device=...') LustreError: 7448:0:(obd_mount.c:1637:lmd_parse()) Bad mount options LustreError: 7448:0:(tgt_mount.c:2627:lustre_tgt_fill_super()) Unable to mount (-22) "auster exited unexpectedly"
Test session details:
Interop
Client
Lustre: 2.17.58_2_ge5fe6fa
Branch: master
Build: https://build.whamcloud.com/job/lustre-reviews/130995
Kernel: 5.14.0-611.55.1.el9_7.x86_64
Server
Lustre: 2.17.0
Branch: b2_17
Build: https://build.whamcloud.com/job/lustre-b2_17/4
Kernel: 5.14.0-611.13.1_lustre.el9.x86_64
This appears to have started on 2026-08-27 after some patch landing:
https://testing.whamcloud.com/search?client_branch=master&server_branch=b2_17&test_set_script_id=5e9346a2-09e0-11e9-a2cc-52540065bddc&sub_test_script_id=5ebdde12-09e0-11e9-a2cc-52540065bddc&start_date=2026-08-25&end_date=2026-09-09&source=sub_tests#redirect
VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
lustre-initialization lustre-initialization - "auster exited unexpectedly"
- is related to
-
LU-12514 separate out the lustre mount code for server and clients
-
- Open
-