Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
3
-
9223372036854775807
Description
The following scenario is possible:
[root@client client]# lfs setstripe -E100M -c1 -p flash -E-1 -p not_a_pool test [root@client client]# lfs getstripe test test lcm_layout_gen: 2 lcm_mirror_count: 1 lcm_entry_count: 2 lcme_id: 1 lcme_mirror_id: 0 lcme_flags: init lcme_extent.e_start: 0 lcme_extent.e_end: 104857600 lmm_stripe_count: 1 lmm_stripe_size: 1048576 lmm_pattern: raid0 lmm_layout_gen: 0 lmm_stripe_offset: 1 lmm_pool: flash lmm_objects: - 0: { l_ost_idx: 1, l_fid: [0x100010000:0x83:0x0] } lcme_id: 2 lcme_mirror_id: 0 lcme_flags: 0 lcme_extent.e_start: 104857600 lcme_extent.e_end: EOF lmm_stripe_count: 1 lmm_stripe_size: 1048576 lmm_pattern: raid0 lmm_layout_gen: 0 lmm_stripe_offset: -1 lmm_pool: not_a_pool
"lfs" should check if the specified pool "not_a_pool" exists before generate and write the layout (trusted.lov) on the filesystem.
The issue does not exist with plain layout:
[root@client client]# lfs setstripe -c-1 -p not_a_pool test
lfs setstripe: pool 'lustrefs.not_a_pool' does not exist: Invalid argument (22)
Attachments
Issue Links
- is related to
-
LU-11264 llapi_* routines demonstrate poor performance
- Open