From: Hans Reiser <reiser@namesys.com>
To: PFC <lists@boutiquenumerique.com>,
Alexander Zarochentcev <zam@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: [2.6 patch] fs/reiser4/: possible cleanups
Date: Sat, 29 Oct 2005 09:09:04 -0700 [thread overview]
Message-ID: <43639EA0.5080300@namesys.com> (raw)
In-Reply-To: <op.szejazspth1vuj@localhost>
PFC wrote:
>
> 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....
Hans
next prev parent reply other threads:[~2005-10-29 16:09 UTC|newest]
Thread overview: 12+ 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 [this message]
2005-10-29 22:21 ` fsck --rebuild-tree just because my battery ran out PFC
-- strict thread matches above, loose matches on Subject: below --
2005-11-18 3:33 [2.6 patch] fs/reiser4/: possible cleanups Adrian Bunk
2005-11-18 8:24 ` Hans Reiser
2005-11-18 8:31 ` Arjan van de Ven
2005-11-18 18:04 ` Hans Reiser
2005-12-12 1:35 Adrian Bunk
2005-12-12 6:29 ` Hans Reiser
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=43639EA0.5080300@namesys.com \
--to=reiser@namesys.com \
--cc=lists@boutiquenumerique.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.