Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 12
hi every body when i am umount a /dev/mapper/VolGroup00-LOgvol00 its showing umount: /: device is busy. so what to do now...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Nov 2012
    Posts
    32

    umount device is busy


    hi every body when i am umount a /dev/mapper/VolGroup00-LOgvol00
    its showing umount: /: device is busy.
    so what to do now

  2. #2
    Linux Newbie
    Join Date
    Jan 2013
    Posts
    116
    check what file system mounted and if any application running on it.
    if something running then stop the service or application.

  3. #3
    Just Joined!
    Join Date
    Sep 2012
    Location
    India
    Posts
    29
    Hi

    Check where the logical Volume /dev/mapper/VolGroup00-LOgvol00 is mounted.

    you can type
    Code:
    mount
    to list all mounts.

    once you list mount point location, Checked if app is running.
    then umount /mount-point


    Best Regards.

  4. $spacer_open
    $spacer_close
  5. #4
    Just Joined!
    Join Date
    Nov 2012
    Posts
    32
    thanx for reply
    after typing mount command the output i get is
    /dev/mapper/VolGroup-Logvol00 on / ext3 (rw). how to check whc app is running?

  6. #5
    Linux Engineer
    Join Date
    Apr 2012
    Location
    Virginia, USA
    Posts
    913
    / is the root file system. You cannot unmount that directory while the system is running.

    What are you trying to accomplish exactly, maybe we can be of more direct assistance?

  7. #6
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,691
    You will get this error any time you try to umount a device that has any file/directory open when you do so, including just having a shell cd'd to a directory there. This is not uncommon. It happens to me all the time, and usually it is just that I have a shell somewhere that either has a file opened on that device, or I have a shell located there.

    If you want (not safe for prime time), you can use the -f (force) option to force the unmounting of the file system - caveat user!
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  8. #7
    Linux Enthusiast
    Join Date
    Jan 2005
    Location
    Saint Paul, MN
    Posts
    668
    Since it is mounted on "/", it can not be unmounted while the OS is running as the process "init" has it busy (which is started by the kernel right after it is loaded and initialized) and it is the parent/ancestor of all jobs running on the system.

  9. #8
    Just Joined!
    Join Date
    Feb 2010
    Location
    Berlin, Germany
    Posts
    17
    You can information about which processes are using a partition or device by typing

    Code:
    lsof '/dev/sdX'
    or

    Code:
    fuser '/dev/sdX'
    This should give the process and its user including its process ID, which you can then end/kill.

    A radical way to kill all processes using a partition or a device would be:

    Code:
    fuser -k '/dev/sdX''

  10. #9
    Just Joined!
    Join Date
    Nov 2012
    Posts
    32
    hiiiiii
    thanx for the reply when i enter the command: fuser -cu /dev/mapper//VolGroup00-LogVol00 the output i get is:

    /dev/mapper//VolGroup00-LogVol00: 1rce(root) 2rc(root) 3rc(root) 4rc(root) 5rc(root) 6rc(root) 7rc(root) 9rc(root) 10rc(root) 12rc(root) 13rc(root) 177rc(root) 181rc(root) 183rc(root) 244rc(root) 245rc(root) 246rc(root) 247rc(root) 248rc(root) 455rc(root) 485rc(root) 486rc(root) 487rc(root) 490rc(root) 491rc(root) 496rc(root) 505rc(root) 516rc(root) 542rc(root) 1354rc(root) 2022rc(root) 2023rc(root) 2086rc(root) 2087rc(root) 2209rc(root) 2244rc(root) 2248rc(root) 2249rc(root) 2250rc(root) 2252rc(root) 2256rc(root) 2264rc(root) 2585rc(root) 2668rc(root) 4392rce(root) 4393rce(root) 4394rce(root) 4404rce(root) 4405rce(root) 4406rce(root) 4407rce(root) 4428rce(root) 4430rce(root) 4431rce(root) 4443rce(root) 4479rce(root) 4508rce(root) 4509rce(root) 4515rce(root) 4518rce(root) 4520rce(root) 4540rce(root) 4544rce(root) 4546rce(root) 4550rce(root) 4552rce(root) 4557rce(root) 4590rce(root) 4596rce(root) 4598rce(root) 4604rce(root) 4611rce(root) 4623rce(root) 4624rce(root) 4632rce(root) 4637rce(root) 4641rce(root) 4659rce(root) 4660rce(root) 4662rce(root) 4674rce(root) 4723rce(root) 4771rce(root) 4773rce(apache) 4774rce(apache) 4775rce(apache) 4776rce(apache) 4777rce(apache) 4778rce(apache) 4779rce(apache) 4780rce(apache) 4829rce(rpc) 4872rce(root) 5076rce(root) 5164rce(mysql) 5288rce(root) 5515rce(root) 5518rc(root) 5519rc(root) 5520rc(root) 5521rc(root) 5522rc(root) 5523rc(root) 5524rc(root) 5525rc(root) 5526rc(root) 5527rc(root) 5530rce(root) 5642rce(root) 5646rce(root) 5650rce(root)

  11. #10
    Just Joined!
    Join Date
    Feb 2013
    Posts
    1

    fuser -m /dev/mapper/VolGroup00-LOgvol00

    Quote Originally Posted by yaswanth4b7 View Post
    hi every body when i am umount a /dev/mapper/VolGroup00-LOgvol00
    its showing umount: /: device is busy.
    so what to do now

    You can unmount...by using this command..


    fuser -m /dev/mapper/VolGroup00-LOgvol00

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •