[LU-17126] sanity-lfsck: ost mount fails with Address already in use Created: 18/Sep/23  Updated: 18/Sep/23

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Unresolved Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for S Buisson <sbuisson@ddn.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/bd151ab7-e941-4898-8bd1-3e9dabddcc5e

Test session details:
clients: https://build.whamcloud.com/job/lustre-reviews/98620 - 4.18.0-477.15.1.el8_8.x86_64
servers: https://build.whamcloud.com/job/lustre-reviews/98620 - 4.18.0-477.15.1.el8_lustre.x86_64

We can see the following error at the end of the test suite:

Starting ost4: -o localrecov  /dev/mapper/ost4_flakey /mnt/lustre-ost4
CMD: onyx-45vm8 mkdir -p /mnt/lustre-ost4; mount -t lustre -o localrecov  /dev/mapper/ost4_flakey /mnt/lustre-ost4
onyx-45vm8: mount.lustre: mount /dev/mapper/ost4_flakey at /mnt/lustre-ost4 failed: Address already in use
onyx-45vm8: The target service's index is already in use. (/dev/mapper/ost4_flakey)
pdsh@onyx-71vm1: onyx-45vm8: ssh exited with exit code 98

Generated at Sat Feb 10 03:32:51 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.