[LU-4866] The ost-survey script from the lustre-iokit in build-41 of the SLES11SP3 lustre RPMs reports obsolete usage of lfs setstripe.

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.5.0
• Type: Bug
• Priority: Minor
• Reporter: Bart Willems (Inactive)
• Assignee: Keith Mannthey (Inactive)
• Resolution: Won't Fix

Environment

SLES 11 SP3
lustre-b2_5 build-41
kernel 3.0.101-0.15_lustre-default

• Epic/Theme: IOkit
• Severity: 3
• Epic: performance

Description

1. ost-survey -s 10 /lustre/
   /usr/bin/ost-survey: 04/05/14 OST speed survey on /lustre/ from 192.169.53.147@o2ib
   Number of Active OST devices : 24
   error: obsolete usage of setstripe positional parameters. Use -c, -i, -S instead.
   Create a new file with a specific striping pattern or
   set the default striping pattern on an existing directory or
   delete the default striping pattern from an existing directory
   usage: setstripe -d <directory> (to delete default striping)
   or
   usage: setstripe [--stripe-count|-c <stripe_count>]
   [--stripe-index|-i <start_ost_idx>]
   [--stripe-size|-S <stripe_size>]
   [--pool|-p <pool_name>]
   [--block|-b] <directory|filename>
   stripe_size: Number of bytes on each OST (0 filesystem default)
   Can be specified with k, m or g (in KB, MB and GB
   respectively)
   start_ost_idx: OST index of first stripe (-1 default)
   stripe_count: Number of OSTs to stripe over (0 default, -1 all)
   pool_name: Name of OST pool to use (default none)
   block: Block file access during data migration

Comments

[Keith Mannthey (Inactive)]

Bob, do you have any suggestion of why ost-survey might be different on SuSE Lustre?

[Bob Glossman (Inactive)]

Keith, no clue.

error shown complains about using positional args in setstripe instead of -x args. I think positional args were taken out quite a while ago. Nothing SLES specific there, just gone.

Does ost-survey have any distro specific scripts like lbuild does?

[Bob Glossman (Inactive)]

see LU-4527

[John Fuchs-Chesney (Inactive)]

Do we anticipate any further action/progress on this ticket?
If not, shall I mark it as resolved/duplicate?
Thanks,
~ jfc.

[John Fuchs-Chesney (Inactive)]

Let me know if anyone wants to reopen this issue.
Thanks,
~ jfc.