[LU-16749] apply a filter to the configuration log.

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Affects Version/s: Lustre 2.12.9

Epic/Theme

client

• Severity: 3
• Assignee: WC Triage
• Reporter: James Beal

Description

We discovered that a lustre server can have entries in its configuration log which can effect other filesystems. eg

lctl set_param -P llite.*.max_cached_mb=2048

When a filesystem is mounted which has this in the filesystems configuration log, the client will apply the option to all mounted filesystems.

I believe that the client should only apply a configuration option from the log to elements of that filesystem

I can imagine a site which has multiple vendors and for example a vendor putting options in that casued issues for their competitor.

 

Issue Links

• is related to: LU-9912 fix multiple client mounts with different server timeouts
• is related to: LU-8750 Wrong obd_timeout on the client when we have 2 or more lustre fs
• is related to: LU-15246 Add per device adaptive timeout parameters
• is related to: LU-17030 allow setting max_cached_mb with %