From: Andi Kleen <ak@suse.de>
To: Dominik Kubla <kubla@sciobyte.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: implementing soft-updates
Date: 10 Apr 2002 21:24:20 +0200 [thread overview]
Message-ID: <p73adsbpdaz.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20020409184605.A13621@cecm.usp.br.suse.lists.linux.kernel> <200204100041.g3A0fSj00928@saturn.cs.uml.edu.suse.lists.linux.kernel> <20020410092807.GA4015@duron.intern.kubla.de.suse.lists.linux.kernel>
Dominik Kubla <kubla@sciobyte.de> writes:
> The background fsck capability, just like journalling or logging, are
> typically only in needed in 24/7 systems (sure, they are nice to have in
> your home system, but do you _REALLY_ need them? i don't!) and those
> system typically are run on proven hardware which is operated well
> within the specs. So please don't construct these kinds of arguments.
You can already do background fsck on a linux system today. Just do it on
a LVM/EVMS snapshot.
-Andi
next parent reply other threads:[~2002-04-10 19:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020409184605.A13621@cecm.usp.br.suse.lists.linux.kernel>
[not found] ` <200204100041.g3A0fSj00928@saturn.cs.uml.edu.suse.lists.linux.kernel>
[not found] ` <20020410092807.GA4015@duron.intern.kubla.de.suse.lists.linux.kernel>
2002-04-10 19:24 ` Andi Kleen [this message]
2002-04-08 20:35 ` implementing soft-updates Pavel Machek
2002-04-15 20:25 ` Andi Kleen
2002-04-15 20:47 ` Andreas Dilger
2002-04-16 10:45 ` Wichert Akkerman
2002-04-16 18:55 ` Mike Fedyk
2002-04-11 16:35 James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2002-04-09 21:46 Alexis S. L. Carvalho
2002-04-09 22:17 ` Mike Fedyk
2002-04-09 22:23 ` Dominik Kubla
2002-04-09 23:36 ` Mike Fedyk
2002-04-10 0:41 ` Albert D. Cahalan
2002-04-10 1:58 ` Alexis S. L. Carvalho
2002-04-10 3:46 ` Andreas Dilger
2002-04-10 2:55 ` Andreas Dilger
2002-04-10 11:48 ` Peter Wächtler
2002-04-11 12:45 ` Bill Davidsen
2002-04-10 9:28 ` Dominik Kubla
2002-04-10 18:07 ` Albert D. Cahalan
2002-04-08 20:34 ` Pavel Machek
2002-04-10 18:13 ` Andreas Dilger
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=p73adsbpdaz.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=kubla@sciobyte.de \
--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 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.