[LU-8750] Wrong obd_timeout on the client when we have 2 or more lustre fs

• Type: Improvement
• Resolution: Duplicate
• Priority: Minor
• Affects Version/s: Lustre 2.7.0

Epic/Theme

lnet

• Assignee: Hongchao Zhang
• Reporter: Antoine Percher

Description

when we mount 2 or more lustre fs on a client, the obd_timeout is the max of the all server obd_timeout. in some cases, it could be have some server evict due to that one of server does not wait obd_ping request enough time

in my case, I have 2 lustre fs, Servers 2.5.X and some Clients 2.7, the first server have obd_timeout=100 and the second server have obd_timeout=300 so the obd_timeout inherited on the client is obd_timeout=300. the client send one obd-ping request each 75 seconds if just one obd_ping request is lost, the client could be evict, so it could be better to have a obd_timeout by filesystems or the min of the each servers filesystems

Issue Links

• is related to: LU-16749 apply a filter to the configuration log.
• is related to: LU-9912 fix multiple client mounts with different server timeouts
• is related to: LU-8066 Move lustre procfs handling to sysfs and debugfs.
• is related to: LU-15246 Add per device adaptive timeout parameters