From: Andrew Morton <akpm@digeo.com>
To: dipankar@in.ibm.com
Cc: "Henrik Størner" <henrik@hswn.dk>,
"Maneesh Soni" <maneesh@in.ibm.com>,
linux-mm@kvack.org
Subject: Re: 2.5.42-mm2 hangs system
Date: Wed, 16 Oct 2002 12:43:06 -0700 [thread overview]
Message-ID: <3DADC14A.5700CEC@digeo.com> (raw)
In-Reply-To: <20021017010103.C2380@in.ibm.com>
Dipankar Sarma wrote:
>
> On Wed, Oct 16, 2002 at 08:59:08PM +0200, Henrik Storner wrote:
> > well you hit the nail right on the head there.
> >
> > I've just been running the 2.5.42-mm2 kernel except for the dcache_rcu
> > patch for a full hour, and I was unable to reproduce the hangs that I
> > saw with the full -mm2 patch installed. Did two full kernel builds
> > while reading some mail and doing other stuff - no problems what so
> > ever.
> >
> > Just to be sure, I re-applied the dcache_rcu patch, rebuilt the
> > kernel, booted with the kernel containing dcache_rcu patch,
> > and the system died within a few minutes.
> >
> > So it is definitely something in the dcache_rcu patch that does it.
>
> Well, I am not quite sure of this yet. Maneesh pointed out this earlier -
> In this machine with 2.5.42-mm2 and no dcache_rcu, (with your .config),
> we see this -
>
> [root@llm04 dbench]# df
> Filesystem 1k-blocks Used Available Use% Mounted on
> /dev/sda6 1004024 461168 491852 49% /
> /dev/sda1 505605 38348 441153 8% /boot
> /dev/sda5 2514172 1791560 594900 76% /usr
> none 257532 0 257532 0% /dev/shm
> /dev/sdb5 6324896 23996 5979604 1% /mnt/sdb5
> llm04:/mnt/sdb5 6324896 23968 5979616 1% /mnt/sdc1
> /dev/sda2 9068648 3993040 4614948 47% /home
> [root@llm04 dbench]# pwd
> /mnt/sdc1/dbench
> root@llm04 dbench]# ./dbench 4
> 4 clients started
> ..........................................................................................................................................rmdir CLIENTS/CLIENT2/~DMTMP/WORDPRO failed (Directory not empty)
> rmdir CLIENTS/CLIENT2/~DMTMP/PARADOX failed (Directory not empty)
Is this dbench-on-NFS? That has always failed - it's to do
with the funny NFS handling of unlinked-while-open files.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-10-16 19:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 16:04 Henrik Størner
2002-10-13 21:03 ` William Lee Irwin III
[not found] ` <3DA9CA28.155BA5CB@digeo.com>
2002-10-13 22:33 ` Henrik Størner
2002-10-13 22:57 ` Andrew Morton
2002-10-14 12:25 ` 2.5.42-mm2 on small systems Ed Tomlinson
2002-10-14 14:34 ` Martin J. Bligh
2002-10-14 21:24 ` Bill Davidsen
2002-10-15 6:42 ` Andrew Morton
2002-10-16 20:55 ` Bill Davidsen
2002-10-16 22:43 ` Ed Tomlinson
2002-10-16 13:09 ` 2.5.42-mm2 hangs system Maneesh Soni
2002-10-16 15:49 ` Henrik Størner
2002-10-16 18:59 ` Henrik Størner
2002-10-16 19:31 ` Dipankar Sarma
2002-10-16 19:43 ` Andrew Morton [this message]
2002-10-16 20:05 ` Dipankar Sarma
2002-10-30 9:48 ` [FIX] " Maneesh Soni
2002-10-31 7:54 ` Henrik Størner
2002-10-17 14:38 ` Maneesh Soni
2002-10-17 16:14 ` 2.5.43-mm2 gets network connection stuck Sebastian Benoit
2002-10-17 17:22 ` Andrew Morton
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=3DADC14A.5700CEC@digeo.com \
--to=akpm@digeo.com \
--cc=dipankar@in.ibm.com \
--cc=henrik@hswn.dk \
--cc=linux-mm@kvack.org \
--cc=maneesh@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox