From: Michael Tokarev <mjt@tls.msk.ru>
To: Steven Rostedt <rostedt@goodmis.org>
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, 07 Oct 2005 20:38:05 +0400 [thread overview]
Message-ID: <4346A46D.7010105@tls.msk.ru> (raw)
In-Reply-To: <Pine.LNX.4.58.0510071017550.7222@localhost.localdomain>
Steven Rostedt wrote:
> 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
Looks like it's more reproduceable when there's some writing
going on at this point - after enabling the quotas and before
remointing it read-only. Maybe there's some unwritten quota
data left in memory at the remount, or something like that...
>> # 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.
I'm able to reproduce it on almost any my machine. Tried on several
production machines first ;) And on at least two test machines.
Now I'm at home and my home PC also shows this bug (2.6.13.1 vanilla).
> Have you tried turning on the nmi watchdog with "nmi_watchdog=2 lapic"?
nmi_watchdog makes no visible difference. Lapic is already enabled, at
least on this machine (BTW, the same behaviour happens on SMP and UP
machines, with and without hyperthreading enabled).
> 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.
And hee-hoo, sysrq works! Strange I haven't noticied it before - I think
I tried it on the laptop, maybe I pressed some wrong button...
Now, as I don't have another PC here @home, only this machine and an ADSL
router (small mips-based device wich is also running linux), and I will
not have access to another machine(s) till monday... I'll try netconsole
to the router. Damn, why ShiftPgUp does not work as it worked in 2.4?? :(
/mjt
next prev parent reply other threads:[~2005-10-07 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 13:13 kernel freeze (not even an OOPS) on remount-ro+umount when using quotas Michael Tokarev
2005-10-07 13:30 ` Michael Tokarev
2005-10-07 14:21 ` Steven Rostedt
2005-10-07 16:38 ` Michael Tokarev [this message]
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=4346A46D.7010105@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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 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.