[LU-3893] lfs getstripe in nested directories does not indicate pools exist

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Severity: 3
• Assignee: WC Triage
• Reporter: Colin Faber [X] (Inactive)

Description

When assigning a directory an OST pool, nested (sub) directories fail to indicate that they have a pool assigned to them when queried with lfs getstripe

All looks good so far..

[root@coolermaster lustre]# lfs getstripe test
test
stripe_count:   -1 stripe_size:    1048576 stripe_offset:  -1 pool:           test 

[root@coolermaster lustre]# cd test
[root@coolermaster test]# touch y
[root@coolermaster test]# lfs getstripe y
y
lmm_stripe_count:   1
lmm_stripe_size:    1048576
lmm_layout_gen:     0
lmm_stripe_offset:  0
lmm_pool:           test
        obdidx           objid           objid           group
             0               4            0x4                0

Um.. where did pool info go???

[root@coolermaster test]# mkdir x
[root@coolermaster test]# lfs getstripe x
x
stripe_count:   -1 stripe_size:    1048576 stripe_offset:  -1 

Creating a file, indicates that the pool is infact inhieritied

[root@coolermaster test]# cd x
[root@coolermaster x]# touch y
[root@coolermaster x]# lfs getstripe y
y
lmm_stripe_count:   1
lmm_stripe_size:    1048576
lmm_layout_gen:     0
lmm_stripe_offset:  0
lmm_pool:           test
        obdidx           objid           objid           group
             0               5            0x5                0

There also seems to be another bug here, lfs getstripe format changes depending on output context.