[LU-3799] Interop 2.1.5<->2.5 failure on test suite replay-single test_0d: mount fails Created: 20/Aug/13 Updated: 09/Jan/20 Resolved: 09/Jan/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.5.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | Nathaniel Clark |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
server: lustre-master build #1617 |
||
| Severity: | 3 |
| Rank (Obsolete): | 9817 |
| Description |
|
This issue was created by maloo for sarah <sarah@whamcloud.com> This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/71cd2a80-06df-11e3-87de-52540035b04c. The sub-test test_0d failed with the following error:
test log shows: Started lustre-MDT0000 Starting client: client-23-ib.lab.whamcloud.com: -o user_xattr,acl,flock client-20-ib@o2ib:/lustre /mnt/lustre CMD: client-23-ib.lab.whamcloud.com mkdir -p /mnt/lustre CMD: client-23-ib.lab.whamcloud.com mount -t lustre -o user_xattr,acl,flock client-20-ib@o2ib:/lustre /mnt/lustre mount.lustre: according to /etc/mtab client-20-ib@o2ib:/lustre is already mounted on /mnt/lustre replay-single test_0d: @@@@@@ FAIL: mount fails |
| Comments |
| Comment by Oleg Drokin [ 21/Aug/13 ] |
|
so mount failed with "already mounted" because earlier unmount failed: umount: /mnt/lustre: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
|
| Comment by Nathaniel Clark [ 25/Sep/13 ] |
|
This is a little hard to debug since maloo currently has no log files for this report. |
| Comment by Peter Jones [ 26/Sep/13 ] |
|
Nathaniel How about using test params to force a repeat run (or multiple repeat runs) of the offending test and see whether it reproduces or not? Peter |
| Comment by Nathaniel Clark [ 27/Sep/13 ] |
|
I haven't been able to reproduce this in testing (client: v2.1.5 server:master ~v2.4.93), and I don't see any other occurrences in maloo. |
| Comment by Peter Jones [ 12/Feb/14 ] |
|
ok so let's close the ticket for now and reopen or open a new one if this ever does reoccur in the future. |
| Comment by Andreas Dilger [ 09/Jan/20 ] |
|
Close old bug |