[LU-5729] VFS: Busy inodes after unmount of loop0. Self-destruct in 5 seconds. Have a nice day... Created: 13/Oct/14  Updated: 04/May/17  Resolved: 02/Dec/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.7.0

Type: Bug Priority: Major
Reporter: Sergey Cheremencev Assignee: James Nunez (Inactive)
Resolution: Fixed Votes: 0
Labels: patch

Issue Links:
Related
is related to LU-5986 conf-sanity test_83, test_84: failed ... Resolved
is related to LU-6207 conf-sanity test_83: test failed to r... Resolved
is related to LU-9433 sanity-scrub test_6: Error in dmesg d... Resolved
is related to LU-6468 Interop 2.5.3<->master conf-sanity te... Resolved
Severity: 3
Rank (Obsolete): 16089

 Description   

Extra inode decrement is needed for scrub->os_inode(OI_scrub) in osd_scrub_setup in case of ENOSPACE error.
It is simple to reproduce:

  1. mount ost as ldiskfs to mntpt
  2. fill mnt point to get ENOSPACE later(llverfs may be used for that)
  3. umount ost
  4. delete scrub files using writeconf
  5. mount ost

These causes kernel message like below:

VFS: Busy inodes after unmount of loop0. Self-destruct in 5 seconds. Have a nice day...

xyratex-bug-id: MRP-2109

 Comments   
Comment by Sergey Cheremencev [ 13/Oct/14 ]

Here is the patch with a test to reproduce the issue
http://review.whamcloud.com/#/c/12283/
fix:
http://review.whamcloud.com/#/c/12284/

Comment by Sergey Cheremencev [ 17/Oct/14 ]

merged test(12283) and fix(12284) into http://review.whamcloud.com/#/c/12325/

Comment by Peter Jones [ 22/Oct/14 ]

James

Could you please take care of this patch?

Thanks

Peter

Comment by Gerrit Updater [ 19/Nov/14 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/12325/
Subject: LU-5729 osd: iput in case of error in osd_scrub_setup
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: b474a0320e83daeffa44eccf724a19641d3f6566

Comment by James Nunez (Inactive) [ 02/Dec/14 ]

Landed to master (pre-2.7).

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