[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090831180746.GA32110@piper.oerlikon.madduck.net>
Date: Mon, 31 Aug 2009 20:07:46 +0200
From: martin f krafft <madduck@...ian.org>
To: Jesse Brandeburg <jesse.brandeburg@...il.com>
Cc: Theodore Tso <tytso@....edu>, Pavel Machek <pavel@....cz>,
NeilBrown <neilb@...e.de>, Ric Wheeler <rwheeler@...hat.com>,
Rob Landley <rob@...dley.net>, Florian Weimer <fweimer@....de>,
Goswin von Brederlow <goswin-v-b@....de>,
kernel list <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...l.org>, mtk.manpages@...il.com,
rdunlap@...otime.net, linux-doc@...r.kernel.org,
linux-ext4@...r.kernel.org, corbet@....net
Subject: Re: raid is dangerous but that's secret (was Re: [patch] ext2/3:
document conditions when reliable operation is possible)
also sprach Jesse Brandeburg <jesse.brandeburg@...il.com> [2009.08.31.1949 +0200]:
> In the case of a degraded array, could the kernel be more
> proactive (or maybe even mdadm) and have the filesystem remount
> itself withOUT journalling enabled? This seems on the surface to
> be possible, but I don't know the internal particulars that might
> prevent/allow it.
Why would I want to disable the filesystem journal in that case?
--
.''`. martin f. krafft <madduck@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
"i can stand brute force, but brute reason is quite unbearable. there
is something unfair about its use. it is hitting below the
intellect."
-- oscar wilde
Download attachment "digital_signature_gpg.asc" of type "application/pgp-signature" (198 bytes)
Powered by blists - more mailing lists