[LU-5213] conf-sanity test_45: umount2: Device or resource busy Created: 17/Jun/14  Updated: 16/Dec/14  Resolved: 16/Dec/14

Status: Closed
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.6.0
Fix Version/s: None

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

server and client: lustre-master build #2091

Issue Links:
Related
is related to LU-1882 conf-sanity test_45: umount2: Device ... Resolved
Severity: 3
Rank (Obsolete): 14547

 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/0fa3ce68-f522-11e3-b29e-52540035b04c.

The sub-test test_45 failed with the following error:

test_45 failed with 3

CMD: shadow-49vm6.shadow.whamcloud.com lctl set_param fail_loc=0x50f
fail_loc=0x50f
sleep 10 sec
manual umount lustre on /mnt/lustre....
CMD: shadow-49vm6.shadow.whamcloud.com umount -d --force /mnt/lustre
umount2: Device or resource busy
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))
df: `/mnt/lustre'umount2: Device or resource busy
: Cannot send after transport endpoint shutdown
df: no file systems processed
 conf-sanity test_45: @@@@@@ FAIL: test_45 failed with 3


 Comments   
Comment by Andreas Dilger [ 18/Jun/14 ]

How is this bug different from LU-1882?

Comment by Sarah Liu [ 16/Dec/14 ]

dup of LU-1882

Generated at Sat Feb 10 01:49:30 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.