From: florin@iucha.net (Florin Iucha)
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.20-rc1: CIFS cheers, NFS4 jeers
Date: Mon, 26 Feb 2007 00:45:00 -0600 [thread overview]
Message-ID: <20070226064500.GZ29073@iucha.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
Hello, it's me and my 70 GB of photos again.
I have tested both CIFS and NFSv4 clients in kernel 2.6.20-rc1 . CIFS
passed with flying colors and NFSv4 stalled after 7 GB.
Configuration:
Server: PIII/1GHz, 512 MB RAM, Debian testing,
distro kernel 2.6.18-3-vserver-686, Intel E1000 NIC,
filesystem 170 GB ext3 with default mkfs values on a SATA disk
Client: AMD x2 4200+, 2 GB RAM, Debian testing/unstable
kernel 2.6.20-rc1, Marvell SKGE onboard,
filesystem 120 GB ext3 with default mkfs values on a SATA disk
After the writing stalls, I have echoed 't' into /proc/sysrq-trigger
and got a trace, which is at http://iucha.net/20-rc1/after.1. There was
no oops before the trace request; the 'before' dmesg is at
http://iucha.net/20-rc1/before.1 .
Running 'top', one core is idle and the other is 99% waiting, while
the 'cp' program is in 'D' state. Also, after NFSv4 stalls, invokations
of 'lsof' stall as well. I can 'ssh' into the box without problems.
florin
--
Bruce Schneier expects the Spanish Inquisition.
http://geekz.co.uk/schneierfacts/fact/163
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-02-26 6:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 6:45 Florin Iucha [this message]
2007-02-26 6:48 ` Correction 2.6.21-rc1 Was: 2.6.20-rc1: CIFS cheers, NFS4 jeers Florin Iucha
2007-02-28 2:36 ` Bill Davidsen
2007-02-28 4:03 ` 2.6.21-rc1: " Florin Iucha
2007-02-28 13:35 ` Bill Davidsen
2007-03-01 5:52 ` 2.6.20-rc1: " Andrew Morton
2007-03-02 3:02 ` Florin Iucha
2007-03-02 14:39 ` Florin Iucha
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=20070226064500.GZ29073@iucha.net \
--to=florin@iucha.net \
--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