public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lazy umount (1/4)
Date: Sat, 15 Sep 2001 13:51:18 -0700	[thread overview]
Message-ID: <20010915135118.A24067@mikef-linux.matchmail.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0109141427070.11172-100000@weyl.math.psu.edu> <20010915083236.A9271@bessie.localdomain>
In-Reply-To: <20010915083236.A9271@bessie.localdomain>

On Sat, Sep 15, 2001 at 08:32:36AM -0400, jlnance@intrex.net wrote:
> On Fri, Sep 14, 2001 at 03:01:26PM -0400, Alexander Viro wrote:
> 
> > convenient when you are doing fs hacking ;-)  Actually I've got into
> > a habit of using that instead of normal umount in all cases except
> > the shutdown scripts - works just fine (for obvious reasons in case
> > of shutdown non-lazy behaviour is precisely what we want).
> 
> Why not shutdown?  This is the place I think it would help me the most.
> 
> Thanks,
> 
> Jim

If you have a FS with a process stuck in D state, and you shutdown with an
umount that *always* does lazy unmounting you get the same affect, because
you'd want the kernel to pause the shutdown until the FS was properly
unmounted.

Either way, you'd have a system you can't reboot without hardware reset if
you have a process stuck in D state on a rw FS.

I have a system with badblocks and shutdown stuck in D state.  Kernel is
2.2.19 on PPC with the freeswan1.9 patch.

It has been stuck for about two weeks, but operating normally otherwise.
I'm going to have to sync; sync; and power off, as I need to update the
kernel anyway.

I too would like to see a way to force umount, but I don't see a safe way.
OTOH, I'm also not a kernel hacker.  Does anyone see a solution?

Mike

  reply	other threads:[~2001-09-15 20:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-14 19:01 [PATCH] lazy umount (1/4) Alexander Viro
2001-09-14 19:02 ` [PATCH] lazy umount (2/4) Alexander Viro
2001-09-14 19:03   ` [PATCH] lazy umount (3/4) Alexander Viro
2001-09-14 19:03     ` [PATCH] lazy umount (4/4) Alexander Viro
2001-09-14 20:43 ` [PATCH] lazy umount (1/4) Linus Torvalds
2001-09-14 20:54   ` Alexander Viro
2001-09-15 12:32 ` jlnance
2001-09-15 20:51   ` Mike Fedyk [this message]
2001-09-17 10:06     ` Matthias Andree
2001-09-16 16:37 ` Alex Stewart
2001-09-17  6:57   ` Forced umount (was lazy umount) Ville Herva
2001-09-17  7:03     ` Aaron Lehmann
2001-09-17  8:38       ` Alexander Viro
2001-09-17 10:21         ` Matthias Andree
2001-09-17 10:47           ` Tigran Aivazian
2001-09-17 23:21             ` Alex Stewart
2001-09-17 23:23               ` Xavier Bestel
2001-09-18  1:04                 ` Alex Stewart
2001-09-18 20:19                   ` Pavel Machek
2001-09-17  8:29     ` Xavier Bestel
2001-09-17  8:39       ` Alexander Viro
2001-09-17 10:04 ` [PATCH] lazy umount (1/4) Matthias Andree
2001-09-17 12:13   ` Alan Cox
2001-09-18  0:24     ` Alex Stewart
2001-09-18  0:39       ` Matthias Andree
2001-09-18  8:56         ` Alexander Viro
2001-09-18  9:08           ` Matthias Andree
2001-09-18 13:03             ` Alan Cox
2001-09-18  9:07     ` David Woodhouse
2001-09-17 14:43 ` David Woodhouse

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=20010915135118.A24067@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=linux-kernel@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