All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2002-Q4@gmx.net>
To: root@chaos.analogic.com
Cc: Alexander Viro <viro@math.psu.edu>,
	Tigran Aivazian <tigran@veritas.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Forced umount
Date: Fri, 18 Oct 2002 22:25:33 +0200	[thread overview]
Message-ID: <3DB06E3D.8050704@gmx.net> (raw)
In-Reply-To: Pine.LNX.3.95.1021018151840.150A-100000@chaos.analogic.com

Richard B. Johnson wrote:
> On Fri, 18 Oct 2002, Carl-Daniel Hailfinger wrote:
> [SNIPPED,,,]
> 
>>To put it another way: Is there any chance to umount / cleanly if / is local
>>and /smbserver is a mounted remote SMB filesystem where the network link to
>>the SMB server just went down? (Without waiting half an hour for a timeout.)
>>
> You don't need to unmount a network drive (or any drive)
> from a mount-point on a file-system before you umount that
> file-system!
> 
> In other words, if I have quark:/tmp mounted on /tmp, I can
> umount / without unmounting quark:/tmp. 
> 
 > [SNIPPED]

Does not work here.

# mount /dev/fd0 /floppy/
# mount /dev/hda1 /floppy/test/
# umount /floppy/
umount: /media/floppy: device is busy
# touch /floppy/foo
umount -f /floppy/
umount2: Device or resource busy
umount: /dev/fd0: not mounted
umount: /media/floppy: Illegal seek
# touch /floppy/foo2
# mount
/dev/fd0 on /floppy type vfat (rw,sync)
/dev/hda1 on /floppy/test type vfat (rw)

In other words, your suggested method does not work here. (Kernel 2.4.18, 
util-linux-2.11n)

# mount -o remount,ro /floppy/
/dev/fd0 on /floppy type vfat (ro,sync)
/dev/hda1 on /floppy/test type vfat (rw)

This, however, seems to work.

Regards,

Carl-Daniel


  reply	other threads:[~2002-10-18 20:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 18:41 Forced umount Carl-Daniel Hailfinger
2002-10-18 19:20 ` Richard B. Johnson
2002-10-18 20:25   ` Carl-Daniel Hailfinger [this message]
2002-10-19 14:28     ` Denis Vlasenko

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=3DB06E3D.8050704@gmx.net \
    --to=c-d.hailfinger.kernel.2002-q4@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --cc=tigran@veritas.com \
    --cc=viro@math.psu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.