public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: kernel freeze (not even an OOPS) on remount-ro+umount when using quotas
Date: Fri, 07 Oct 2005 17:13:32 +0400	[thread overview]
Message-ID: <4346747C.2080903@tls.msk.ru> (raw)

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.

According to the themperature sensors on my test laptop and CPU fan
behaviour, the kernel goes to some infinite loop at this point, because
the fan starts rotating in a few sec after the freeze.

This happens with both quota_v1 and quota_v2.

Note that it isn't 100% reproduceable - sometimes it umounts
ok, sometimes (rare) there's no need to do that pre-final
'ls -l', and sometimes more "work" is needed around remount-ro
to trigger the freeze.

The filesystem is ext3.

Any hints on the way to debug the problem?

Thanks.

/mjt

             reply	other threads:[~2005-10-07 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07 13:13 Michael Tokarev [this message]
2005-10-07 13:30 ` kernel freeze (not even an OOPS) on remount-ro+umount when using quotas Michael Tokarev
2005-10-07 14:21 ` Steven Rostedt
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=4346747C.2080903@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --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