From: PFC <lists@boutiquenumerique.com>
To: Hans Reiser <reiser@namesys.com>,
Alexander Zarochentcev <zam@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: fsck --rebuild-tree just because my battery ran out...
Date: Sun, 30 Oct 2005 00:21:03 +0200 [thread overview]
Message-ID: <op.szfhpdihth1vuj@localhost> (raw)
In-Reply-To: <43639EA0.5080300@namesys.com>
I do not know if a laptop battery running out behaves the same as a power
cord yanking, but this fact may be interesting :
As I was just reading some document, with no other activity, the
harddrive had spinned down since a while, and was NOT running (as in NOT
spinning) when the battery ran out. So it seems, the HD had spinned down,
while the FS was in an inconsistent state. Strange.
This happened several times, out of which, once I had to fsck, and the
other to --rebuild-tree.
linux-2.6.11-cko1-swsusp2
reiser4
gentoo
Centrino Pentium M laptop
cat /proc/sys/vm/laptop_mode
0
/dev/hda:
multcount = 16 (on)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 65535/16/63, sectors = 60011642880, start = 0
I assume the disk flushes its write cache before going to standby (or else
the manufacturers are crazy)...
I hope this can help...
>> Remember my message where I said reiser4 was preventing my laptop
>> from shutting down itself ?
>>
>> Well it turned out that, in fact, it was a stupid shfs-mount
>> process which would refuse to die. Adding a "killall ssh" in the
>> local.stop script is a bit violent, but perfectly functional way, to
>> bring it back to reason. Everything now works.
>>
>> But still, I had to fsck --rebuild-tree just because my battery
>> ran out...
>>
>>
>>
> the battery running out should not have caused you to need to do that.
>
> zam, can you do some testing of how well we handle power cord yanking
> while under load? There are some guys at stanford who have some test
> programs for this sort of thing, I wish I could remember their name at
> the moment....http://www.materiel.net/details_VA7000BWA.html
>
> Hans
>
prev parent reply other threads:[~2005-10-29 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 22:35 [2.6 patch] fs/reiser4/: possible cleanups Adrian Bunk
2005-10-29 3:58 ` Ioan Ionita
2005-10-29 9:22 ` Adrian Bunk
2005-10-29 9:58 ` PFC
2005-10-29 16:09 ` Hans Reiser
2005-10-29 22:21 ` PFC [this message]
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=op.szfhpdihth1vuj@localhost \
--to=lists@boutiquenumerique.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=zam@namesys.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 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.