rm: cannot remove directory `misc': Device or resource busy

简介:

  

rm: cannot remove directory `misc': Device or resource busy

解决方法:

[root@crmnormal misc]# cat /etc/misc

cat: /etc/misc: No such file or directory

[root@crmnormal misc]# cat /etc/auto.master 

#

# $Id: auto.master,v 1.4 2005/01/04 14:36:54 raven Exp $

#

# Sample auto.master file

# This is an automounter map and it has the following format

# key [ -mount-options-separated-by-comma ] location

# For details of the format look at autofs(5).

#

#/misc /etc/auto.misc

#

 这一行注释掉

 

  192  service automount restart 

  193  service autofs restart

解决过程

查看谁在用/misc

[root@crmnormal misc]# /sbin/fuser -m /misc

/misc:                   1rce     2rc     3rc     4rc     5rc     6rc     7rc     8rc     9rc    10rc    11rc    12rc    13rc    14rc    15rc    16rc    17rc    18rc    19rc    20rc    21rc    22rc    23rc    24rc    25rc    26rc   163rc   174rc   175rc   176rc   177rc   178rc   179rc   180rc   181rc   182rc   347rc   348rc   349rc   350rc   351rc   352rc   353rc   354rc   357rc   359rc   483rc   486rc   487rc   488rc   489rc   490rc   491rc   492rc   493rc   494rc   700rc   809rc   810rc   811rc   821rc   822rc   823rc   824rc   825rc   826rc   827rc   828rc   829rc   848rc   885rc   951rc   977rc  1010rce  1390rce  1448rce  1454rce  2588rc  2589rc  2590rc  2591rc  2592rc  2593rc  2594rc  2595rc  2596rc  2663rce  2664rc  2667rc  2668rc  2669rc  2670rc  2671rc  2672rc  2673rc  2674rc  2675rc  2676rc  2679rc  2680rc  2681rc  2682rc  2683rc  2684rc  2685rc  2686rc  2687rce  3254rc  3452rce  3750rce  3752rce  3784rce  3787rce  3920rce  3941rce  3970rce  4004rce  4029rce  4085rce  4100rce  4114rce  4115rce  4125rce  4129rce  4138rce  4191rce  4247rce  4299rce  4337rce  4425rce  4440rce  4454rce  4492rce  4519rce  4556rce  4573rce  4574rce  4659rce  4660rce  4907rce  5029rce  5056rce  5458rce  5462rce  5463rce  5464rce  5467rce  5472rce  5475rce  6738rce  6739rce  6740rce  6741rce  6742rce  6743rce  6744rce  6745rce 14805rc 18963rce 19019rce 19053rce 19109rce 19128rce 19184rce 19204rce 19260rce 19279rce 19335rce 19363rce 19419rce 19450rce 19506rce 21785rce 21800rce 24079rc 29743rce 29753rce 31798rce 31808rce 32649rce 32658rce

[root@crmnormal misc]# lsof +D /misc

COMMAND   PID USER   FD   TYPE DEVICE SIZE    NODE NAME

bash     1454 root  cwd    DIR  253,0 4096 5001376 /misc/crmfile

lsof     5210 root  cwd    DIR  253,0 4096 4933473 /misc

lsof     5211 root  cwd    DIR  253,0 4096 4933473 /misc

bash    29753 root  cwd    DIR  253,0 4096 4933473 /misc

[root@crmnormal crmfile]# exportfs -rv

exporting 192.168.20.28:/misc

exporting 192.168.20.27:/misc

exporting 192.168.20.28:/mnt

exporting 192.168.20.27:/mnt

[root@crmnormal misc]# showmount -e

Export list for crmnormal:

/mnt  192.168.20.27,192.168.20.28

/misc 192.168.20.27,192.168.20.28


本文转自aaa超超aaa 51CTO博客,原文链接:http://blog.51cto.com/10983441/1881281

相关文章
|
Docker 容器
Docker错误:inotify_add_watch(7, /dev/dm-4, 10) failed: No such file or directory
Docker错误:inotify_add_watch(7, /dev/dm-4, 10) failed: No such file or directory
258 1
|
7月前
|
Java
cannot open shared object file: No such file or directory
cannot open shared object file: No such file or directory
90 0
|
网络协议
VFS: Cannot open root device "nfs" or unknown-block(0,255)错误解决
VFS: Cannot open root device "nfs" or unknown-block(0,255)错误解决
570 0
configure: error: Can‘t find ext2fs library
configure: error: Can‘t find ext2fs library
245 0
|
Ubuntu Shell
解决dpkg: warning: files list file for package(libboost-dev libpcl-dev)
解决dpkg: warning: files list file for package(libboost-dev libpcl-dev)
299 0
【问题】Log writing failed, No space left on device @ io_write - /mnt/project/log/development.log
【问题】Log writing failed, No space left on device @ io_write - /mnt/project/log/development.log
185 0
【问题】Log writing failed, No space left on device @ io_write - /mnt/project/log/development.log
|
Linux 虚拟化
【Centos】 kernel panic-not syncing:VFS:Unable to mount root fs on unknown block
背景: VMware虚拟机下 原因: 在命令执行(update)途中,强制中断并直接运行poweroff命令关机。再次开机出现如图所示故障指示: 根据提示信息分析,可能因为执行更新命令未完成导致系统内核信息混乱。
3991 0