public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Coywolf Qi Hunt <coywolf@gmail.com>,
	Lee Revell <rlrevell@joe-job.com>, Marc Perkel <marc@perkel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Forcing an immediate reboot
Date: Sun, 16 Oct 2005 02:10:31 +0200	[thread overview]
Message-ID: <43519A77.2040806@vc.cvut.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0510150909050.25927@hermes-1.csi.cam.ac.uk>

Anton Altaparmakov wrote:
> On Sat, 15 Oct 2005, Coywolf Qi Hunt wrote:
> 
>>On 10/15/05, Anton Altaparmakov <aia21@cam.ac.uk> wrote:
>>
>>>echo s > /proc/sysrq-trigger
>>>echo u > /proc/sysre-trigger
>>>echo s > /proc/sysrq-trigger
>>
>>What the purpose of the second sync?
> 
> 
> Allows any i/o initiated between the first sync and the remount r/o to 
> complete.  Remember that r/o mounting doesn't stop i/o.  It only stops you 
> from writing to the fs at the vfs layer.  Once a write/modification has 
> entered the fs driver it will get written no matter what, unless the 
> "reboot" sysrq is triggered in which case the kernel just reboots 
> immediately.
> 
> Maybe it is just paranoia on my part but I have gotten used to hitting 
> Alt+PrtScr+S, +U, +S, +B so I do it automatically.

Second sync is a must, otherwise remounting read-only is not written to 
the filesystem (at least in my case) so no fsck is saved.   But you can 
save first sync (before remount), and then you get nice sequence which 
even admins comming from Windows can remember - they have to use USB to 
safely reboot their Linux systems ;-)  (alt-sysrq-U, S, B)
								Petr


  reply	other threads:[~2005-10-16  0:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15  1:46 Forcing an immediate reboot Marc Perkel
2005-10-15  1:50 ` Lee Revell
2005-10-15  6:47   ` Coywolf Qi Hunt
2005-10-15  6:51     ` Marc Perkel
2005-10-15  7:48   ` Anton Altaparmakov
2005-10-15  7:56     ` Coywolf Qi Hunt
2005-10-15  8:16       ` Anton Altaparmakov
2005-10-16  0:10         ` Petr Vandrovec [this message]
2005-10-15 13:23     ` documentation? (i learned something today ;-) ) Damir Perisa
2005-10-15 13:40       ` Benoit Boissinot
2005-10-15 14:52         ` Documentation/files somewhere online? Damir Perisa
2005-10-15 15:02           ` Denis Vlasenko
2005-10-15 15:13             ` Michael Krufky
2005-10-15 23:18               ` Documentation/files online: available at git in webinterface Damir Perisa
2005-10-15 14:29     ` Forcing an immediate reboot Marc Perkel
2005-10-15  1:55 ` Randy.Dunlap
2005-10-15  2:24 ` Danny ter Haar
2005-10-15  6:21 ` Willy Tarreau
2005-10-15  6:50   ` Coywolf Qi Hunt
2005-10-15 10:24 ` 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=43519A77.2040806@vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=aia21@cam.ac.uk \
    --cc=coywolf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@perkel.com \
    --cc=rlrevell@joe-job.com \
    /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