From: "bo" <bo@sosnetwork.net>
To: linux-raid@vger.kernel.org
Subject: Couldn't umount on /mnt/md0-device busy???
Date: Wed, 17 Jul 2002 10:35:28 -0700 [thread overview]
Message-ID: <003c01c22db8$57b86590$5701a8c0@bomoon> (raw)
In-Reply-To: 15668.41627.988382.451061@notabene.cse.unsw.edu.au
Hello!
I have found a VERY strange issue on using the name "md0" as a mount point.
If I use "/mnt/md0" as a mount point for the md device or normal HD device,
I could not umount it after booting the system having "device is busy"
error.
However, it is OK if I manually make a RAID then mount it to "/mnt/md0".
I checked if it has any processes running on it with "fuser" but nothing.
Does "/mnt/md0" have a special meaning(usage) for system?
Please provide me a clue.
Thanks,
//Bo
The followins are my experiment on this issue;
root@P3000-PP1:/home/bmoon# cat /proc/mounts
/dev/root / ext2 rw 0 0
none /proc proc rw 0 0
/dev/md0 /mnt/md0 ext2 rw 0 0
/dev/md3 /mnt/md3 ext2 rw 0 0
root@P3000-PP1:/home/bmoon# umount /mnt/md0
umount: /mnt/md0: device is busy
---------------
root@P3000-PP1:/etc# fuser -v /mnt/md0
USER PID ACCESS COMMAND
/mnt/md0 root kernel mount /mnt/md0
----------------after chnage the name of mount point from /mnt/md0 to
/mnt/user---------------
root@P3000-PP1:/home/bmoon# cat /proc/mounts
/dev/root / ext2 rw 0 0
none /proc proc rw 0 0
/dev/md0 /mnt/user ext2 rw 0 0
/dev/md3 /mnt/md3 ext2 rw 0 0
root@P3000-PP1:/home/bmoon# umount /mnt/user
root@P3000-PP1:/home/bmoon#
------------------------
root@P3000-PP1:/etc# vi fstab
/dev/hda2 / ext2 defaults 1 1
none /proc proc defaults 0 0
/dev/hda3 swap swap defaults 0 0
/dev/md0 /mnt/user ext2 defaults 0 0
/dev/md3 /mnt/md3 ext2 defaults 0 0
Another experiment
----------------------
root@P3000-PP1:/home/bmoon# cat /proc/mounts
/dev/root / ext2 rw 0 0
none /proc proc rw 0 0
/dev/hdb2 /mnt/md0 ext2 rw 0 0
/dev/md3 /mnt/md3 ext2 rw 0 0
root@P3000-PP1:/home/bmoon# umount /mnt/md0
umount: /mnt/md0: device is busy
next prev parent reply other threads:[~2002-07-17 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 22:17 reconstruction stalls Michael Robinton
2002-07-16 22:47 ` Neil Brown
2002-07-17 17:35 ` bo [this message]
2002-07-17 18:52 ` Couldn't umount on /mnt/md0-device busy??? Kanoalani Withington
2002-07-18 0:13 ` bo
[not found] ` <009d01c22e54$54d968a0$f6de11cc@black>
2002-07-18 17:11 ` bo
2002-07-18 17:47 ` Ross Vandegrift
2002-07-19 0:43 ` bo
2002-07-19 0:58 ` Ross Vandegrift
2002-07-19 1:49 ` Kanoalani Withington
2002-07-20 8:32 ` Egon Eckert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003c01c22db8$57b86590$5701a8c0@bomoon' \
--to=bo@sosnetwork.net \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).