linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "bo" <bo@sosnetwork.net>
To: Mike Black <mblack@csi-inc.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Couldn't umount on /mnt/md0-device busy???
Date: Thu, 18 Jul 2002 10:11:31 -0700	[thread overview]
Message-ID: <073d01c22e7e$299d8020$5701a8c0@bomoon> (raw)
In-Reply-To: 009d01c22e54$54d968a0$f6de11cc@black

Mike,

It does not matter with the order in /etc/exports.
This "umount" problem goes away when I remove "/mnt/md0" entry from
/etc/exports.  I have 3 more;/mnt/md1, /mnt/md2, /mnt/md3 without any
problem.

I think system has a special meaning with "/mnt/md0".  What does it do???

Any idea?

Bo


----- Original Message -----
From: "Mike Black" <mblack@csi-inc.com>
To: "bo" <bo@sosnetwork.net>
Sent: Thursday, July 18, 2002 5:12 AM
Subject: Re: Couldn't umount on /mnt/md0-device busy???


> Try changing the order in /etc/exports and see if the problem moves.
> Just an idea to test....
>
> ----- Original Message -----
> From: "bo" <bo@sosnetwork.net>
> To: "Kanoalani Withington" <kanoa@cfht.hawaii.edu>
> Cc: <linux-raid@vger.kernel.org>
> Sent: Wednesday, July 17, 2002 8:13 PM
> Subject: Re: Couldn't umount on /mnt/md0-device busy???
>
>
> > Yes, I have 4 entries in /etc/exports; /mnt/md0, /mnt/md1, ..md3.
> > Why do I have this "umount" problem ONLY on /mnt/md0?
> >
> > These 4 entries have the same option and parameters.
> >
> > Any more help will be appreciated.
> >
> > Bo
> > ----- Original Message -----
> > From: "Kanoalani Withington" <kanoa@cfht.hawaii.edu>
> > To: "bo" <bo@sosnetwork.net>
> > Cc: <linux-raid@vger.kernel.org>
> > Sent: Wednesday, July 17, 2002 11:52 AM
> > Subject: Re: Couldn't umount on /mnt/md0-device busy???
> >
> >
> > > There may be an entry for /mnt/md0 in /etc/exports. If there is,
usually
> > > the startup scripts will start an NFS server at boot time and the
> > > filesystem will be busy as long as that daemon is running. If you
mount
> > > the volume after the scripts run a server won't be started and the
> > > volume can be manually unmounted without any errors.
> > >
> > > -Kanoa
> > >
> > > bo wrote:
> > >
> > > >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
> > > >
> > > >
> > > >-
> > > >To unsubscribe from this list: send the line "unsubscribe linux-raid"
in
> > > >the body of a message to majordomo@vger.kernel.org
> > > >More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > > >
> > > >
> > >
> > >
> > >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>


  parent reply	other threads:[~2002-07-18 17:11 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   ` Couldn't umount on /mnt/md0-device busy??? bo
2002-07-17 18:52     ` Kanoalani Withington
2002-07-18  0:13       ` bo
     [not found]         ` <009d01c22e54$54d968a0$f6de11cc@black>
2002-07-18 17:11           ` bo [this message]
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='073d01c22e7e$299d8020$5701a8c0@bomoon' \
    --to=bo@sosnetwork.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=mblack@csi-inc.com \
    /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).