From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: 2.4.17 RAID-1 EXT3 reliable to hang....
Date: Mon, 7 Jan 2002 10:38:43 +0200 [thread overview]
Message-ID: <20020107103843.B1914@mea-ext.zmailer.org> (raw)
In-Reply-To: <20020104163635.A1268@mea-ext.zmailer.org>, <20020104163635.A1268@mea-ext.zmailer.org>; <20020107100022.A1914@mea-ext.zmailer.org> <3C395A2C.B7A24844@zip.com.au>
In-Reply-To: <3C395A2C.B7A24844@zip.com.au>; from akpm@zip.com.au on Mon, Jan 07, 2002 at 12:19:56AM -0800
On Mon, Jan 07, 2002 at 12:19:56AM -0800, Andrew Morton wrote:
> Matti Aarnio wrote:
> > I have partial evidence that EXT3 may be part of the problem,
> > as another machine with RAID-1 disks with EXT2 filesystems
> > is not hanging up when running RedHat 2.4.16-0.9custom kernel.
> > That another machine has, however, IDE disks.
>
> I'd be surprised if an ext3 bug could cause a freeze as solid
> as this one. ext3's write submission patterns are somewhat different
> from other filesystems, and we've exposed a few problem in underlying
> layers in the past because of this. But who knows...
>
> Have you enabled the NMI watchdog? nmi_watchdog=1 on the LILO
> commandline?
# cat /proc/cmdline
auto BOOT_IMAGE=up ro root=905 BOOT_FILE=/boot/vmlinuz-2.4.17up nmi_watchdog=1
This is the apparently stable UP mode kernel, but this option
has been present at all variants, although I don't recall of
what the NMI count was previously -- same or lower than that
of LOC count at /proc/interrupts.
> Also, I'd be inclined to enable all the kernel debug options,
> including SLAB debug.
CONFIG_SCSI_DEBUG=y
CONFIG_JBD_DEBUG=y
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_IOVIRT=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_BUGVERBOSE=y
/Matti Aarnio
next prev parent reply other threads:[~2002-01-07 8:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 14:36 Matti Aarnio
2002-01-07 8:00 ` Matti Aarnio
2002-01-07 8:19 ` Andrew Morton
2002-01-07 8:38 ` Matti Aarnio [this message]
2002-01-07 8:39 ` Oliver Paukstadt
2002-01-07 8:49 ` Andrew Morton
2002-01-07 9:51 ` Richard Guenther
2002-01-07 10:09 ` Andrew Morton
2002-01-07 10:33 ` Richard Guenther
2002-01-20 17:31 ` Matti Aarnio
2002-01-20 19:24 ` John Jasen
2002-01-20 19:57 ` Matti Aarnio
2002-01-21 0:22 ` Oliver Xymoron
2002-01-07 13:45 ` Alan Cox
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=20020107103843.B1914@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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
all inboxes | Powered by JetHome®