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:
signature.asc
Description: Digital signature
- Follow-Ups:
- Correction 2.6.21-rc1 Was: 2.6.20-rc1: CIFS cheers, NFS4 jeers
- From: [email protected] (Florin Iucha)
- Correction 2.6.21-rc1 Was: 2.6.20-rc1: CIFS cheers, NFS4 jeers
- Prev by Date: RE: RFC/patch: down_timeout_interruptible()
- Next by Date: Correction 2.6.21-rc1 Was: 2.6.20-rc1: CIFS cheers, NFS4 jeers
- Previous by thread: [PATCH] sata_mv: fix DMA boundary, 64-bit PCI DMA issues
- Next by thread: Correction 2.6.21-rc1 Was: 2.6.20-rc1: CIFS cheers, NFS4 jeers
- Index(es):