[LU-737] can not attach device name starting with a digit

• Type: Improvement
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.2.0, Lustre 1.8.8
• Affects Version/s: Lustre 2.2.0, Lustre 1.8.7
• Assignee: Minh Diep
• Reporter: Minh Diep

Description

If we assign fsname starting with a digit (ie 1b), the OST devices name will be 1b-OST0000 and this will prevent lctl to work, see below

[root@fat-amd-1 ~]# lctl dl
0 UP mgs MGS MGS 5
1 UP mgc MGC10.10.4.132@tcp 299348e4-2002-b4b5-3a43-44db755a662a 5
2 UP mdt MDS MDS_uuid 3
3 UP lov 1b-mdtlov 1b-mdtlov_UUID 4
4 UP mds 1b-MDT0000 1b-MDT0000_UUID 3
5 UP ost OSS OSS_uuid 3
6 UP obdfilter 1b-OST0000 1b-OST0000_UUID 5
7 UP osc 1b-OST0000-osc 1b-mdtlov_UUID 5
8 AT echo_client 1b-OST0000_ecc 1b-OST0000_ecc_UUID 1
[root@fat-amd-1 ~]# lctl
lctl > device 1b-OST0000_ecc
lctl > cleanup
cleanup: please use 'device name' to set the device name for config commands.
lctl >

I also found out that lustre fsname can be anything except ":". is this a good idea? should we restrict it to unix name format (alpha, number, _)?

Issue Links

• Trackbacks: Changelog 1.8 Changes from version 1.8.7wc1 to version 1.8.8wc1 Server support for kernels: 2.6.18308.4.1.el5 (RHEL5) Client support for unpatched kernels: 2.6.18308.4.1.el5 (RHEL5) 2.6.32220.13.1.el6 (RHEL6) Recommended e2fsprogs version: 1.41.90....
• Trackbacks: Changelog 2.2 version 2.2.0 Support for networks: o2iblnd OFED 1.5.4 Server support for kernels: 2.6.32220.4.2.el6 (RHEL6) Client support for unpatched kernels: 2.6.18274.18.1.el5 (RHEL5) 2.6.32220.4.2.el6 (RHEL6) 2.6.32.360....