From: "Danny Milosavljevic" <danny_milo@yahoo.com>
To: reiserfs-list@namesys.com
Subject: Re: Which version will be merged into mainline kernel?
Date: Mon, 13 Nov 2006 21:27:07 +0000 (UTC) [thread overview]
Message-ID: <ejanvb$dgm$2@sea.gmane.org> (raw)
In-Reply-To: 200611111928.kABJSgre030118@turing-police.cc.vt.edu
Hi,
On Sat, 11 Nov 2006 14:28:42 -0500, Valdis.Kletnieks wrote:
[...]
> I've never understood this kind of attitude some filesystems have. Usually
> the hardware would make sure that stuff doesn't disappear, and not some
> weird software workarounds like journalling or write barriers that
> complicate and slow down everything.
>
> Now as you were saying?
Hehehe. Well, you turned it all around... insightful :)
While we are at it:
I take it that this is the reason journalling support is only picking up
now: the disks are so big that even in the unlikely event that some of the
hardware failsafes fail, one just cannot fsck all the disks completely
anymore, ever.
So the choice is really 'borked once, borked forever' / 'journal it and at
least somehow get it back online without fscking /
copying-to-new-disks-if-at-all-possible for 5 days straight'.
cheers,
Danny
next prev parent reply other threads:[~2006-11-13 21:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 9:50 Which version will be merged into mainline kernel? Clemens Eisserer
[not found] ` <4533D788.3000406@namesys.com>
2006-10-17 21:14 ` Clemens Eisserer
2006-10-17 22:03 ` Maciej Sołtysiak
2006-11-01 13:24 ` Clemens Eisserer
[not found] ` <45495858.6020507@namesys.com>
2006-11-02 9:09 ` Clemens Eisserer
[not found] ` <454A2AB9.3060103@namesys.com>
2006-11-02 19:43 ` Clemens Eisserer
[not found] ` <454A596F.8070909@namesys.com>
2006-11-08 7:21 ` Clemens Eisserer
2006-11-08 9:15 ` Francesco Biscani
2006-11-08 10:21 ` Andreas Dilger
2006-11-08 14:33 ` Clemens Eisserer
[not found] ` <455297E9.1070000@netvigator.com>
2006-11-09 12:57 ` Clemens Eisserer
2006-11-09 18:19 ` Clemens Eisserer
2006-11-11 15:14 ` Danny Milosavljevic
2006-11-11 19:28 ` Valdis.Kletnieks
2006-11-13 21:27 ` Danny Milosavljevic [this message]
2006-11-14 5:51 ` Christopher Chan
2006-11-14 9:16 ` Clemens Eisserer
2006-11-13 3:11 ` Christopher Chan
[not found] ` <45582353.3070709@slaphack.com>
2006-11-13 9:34 ` Christopher Chan
2006-11-13 21:17 ` Danny Milosavljevic
2006-11-14 5:54 ` Christopher Chan
[not found] ` <45589ECD.4070105@slaphack.com>
2006-11-14 6:01 ` Christopher Chan
[not found] ` <455986CB.6010608@slaphack.com>
2006-11-14 10:03 ` Christopher Chan
[not found] ` <455A0E5A.9060404@slaphack.com>
2006-11-15 3:21 ` Christopher Chan
2006-11-15 8:47 ` Clemens Eisserer
2006-11-08 10:35 ` Jindrich Makovicka
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='ejanvb$dgm$2@sea.gmane.org' \
--to=danny_milo@yahoo.com \
--cc=danny.milo@scratchpost.org \
--cc=reiserfs-list@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.