mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel freeze (not even an OOPS) on remount-ro+umount when using quotas
Date: Fri, 7 Oct 2005 10:21:17 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0510071017550.7222@localhost.localdomain> (raw)
In-Reply-To: <4346747C.2080903@tls.msk.ru>


On Fri, 7 Oct 2005, Michael Tokarev wrote:

> This is something that has biten me quite successefully
> in last few days... ;)
>
> To make a long story short:
>
>  # mke2fs -j /dev/hda6
>  # mount -o usrquota /dev/hda6 /mnt
>  # cp -a /home /mnt                # to make some files to work with
>  # quotacheck -uc /mnt
>  # quotaon /mnt
>  # mount -o remount,ro             # this is the important step!
>  # ls -l /mnt /mnt/home            # to do "something" (also important)
>  # umount /mnt
>
> At this time (attempting to umount the read-only filesystem with quotas
> enabled), the machine freezes without any messages on the console.  No
> OOPS, no response, no nothing - until a hard reboot (powercycle).
>
> This happens on 2.6.11, 2.6.12 and 2.6.13 kernels -- ie, with "current"
> kernel release.
>

I just tried this on 2.6.13.1 and was not able to reproduce your hangup.
Have you tried turning on the nmi watchdog with "nmi_watchdog=2 lapic"?

If this blocks interrupts while it spins, you might be able to see what's
happening.  Also if interrupts are not blocked, try out sysrq-t and
friends.

-- Steve


  parent reply	other threads:[~2005-10-07 14:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07 13:13 Michael Tokarev
2005-10-07 13:30 ` Michael Tokarev
2005-10-07 14:21 ` Steven Rostedt [this message]
2005-10-07 16:38   ` Michael Tokarev
2005-10-07 19:12     ` Michael Tokarev

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=Pine.LNX.4.58.0510071017550.7222@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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

all inboxes | Powered by JetHome®