From: Ralf Baechle <ralf@uni-koblenz.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: "ext3-users@redhat.com" <ext3-users@redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: ext3-2.4-0.9.6
Date: Sun, 12 Aug 2001 04:38:41 +0200 [thread overview]
Message-ID: <20010812043841.B8413@bacchus.dhis.org> (raw)
In-Reply-To: <3B75DE86.EEDFAFFB@zip.com.au>
In-Reply-To: <3B75DE86.EEDFAFFB@zip.com.au>; from akpm@zip.com.au on Sat, Aug 11, 2001 at 06:40:22PM -0700
On Sat, Aug 11, 2001 at 06:40:22PM -0700, Andrew Morton wrote:
> - ext3 has for a long time had developer code which allows the target device
> to be turned read-only at the disk device driver level a certain number
> of jiffies after the fs was mounted. This is to allow scripted testing
> of crash recovery. This facility has been extended to support two devices;
> one for the filesystem and one for the external journal device.
Would this facility also be able to deal with parts of a device becoming
read-only unexpectedly? Some of the disks I have in RAIDs have the
nice habit of disabling write access when overheating. That's an
interesting failure scenario in a RAID system.
Ralf
next prev parent reply other threads:[~2001-08-12 2:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 1:40 ext3-2.4-0.9.6 Andrew Morton
2001-08-12 1:46 ` ext3-2.4-0.9.6 Tom Rini
2001-08-12 1:55 ` ext3-2.4-0.9.6 Andrew Morton
2001-08-12 2:15 ` ext3-2.4-0.9.6 Tom Rini
2001-08-12 2:28 ` ext3-2.4-0.9.6 Andrew Morton
2001-08-12 2:47 ` ext3-2.4-0.9.6 Tom Rini
2001-08-12 4:58 ` ext3-2.4-0.9.6 Ben Collins
2001-08-13 18:15 ` ext3-2.4-0.9.6 Andreas Dilger
2001-08-12 2:38 ` Ralf Baechle [this message]
2001-08-12 3:10 ` ext3-2.4-0.9.6 Andrew Morton
2001-08-13 17:56 ` ext3-2.4-0.9.6 Stephen C. Tweedie
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=20010812043841.B8413@bacchus.dhis.org \
--to=ralf@uni-koblenz.de \
--cc=akpm@zip.com.au \
--cc=ext3-users@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox