From: Martin Zabadal <zabadal@afd.cz>
To: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: PROBLEM: XFS on LVM over NFS (Linux) mounted by AIX
Date: Thu, 07 Mar 2002 17:22:03 +0100 [thread overview]
Message-ID: <3C8793AB.5080309@afd.cz> (raw)
Hi experts!
I cannot solve the problem with Linux xfs-1.0.2 on LVM on kernel-2.4.14
and higher served per nfs-server to AIX(4.3.3.0) nfs-clients.
Compiling with the same .config:
1.) kernel-2.4.2 with xfs-1.0 runs nfs excellent with AIX-clients
(except quotas)
2.) kernel-2.4.16 up to 2.4.18 makes use of nfs useless (tranfer rates
about 3kB).
I get the same bad result with precompiled kernel from SGI:
ftp://oss.sgi.com/projects/xfs/download/Release-1.0.2/kernel_rpms/i386/2.4.14/kernel-2.4.14-SGI_XFS_1.0.2.i686.rpm
Here my system: SUSE 7.1
/usr/src/linux/scripts # sh ver_linux
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux pc3 2.4.2-XFS #1 Mon Jul 9 19:47:15 CEST 2001 i686 unknown
Kernel modules 2.4.2
Gnu C 2.95.2 but kernels compiled with egcs 1.1.2
Gnu Make 3.79.1
Binutils 2.10.0.33
Linux C Library x 1 root root 1382179 Dec 18 16:32
/lib/libc.so.6
Dynamic linker ldd (GNU libc) 2.2
Procps 2.0.7
Mount 2.10q
Net-tools 1.57
Kbd 1.02
Sh-utils 2.0
LVM 0.9.4
NFSUTILS 0.2.1-20
Modules Loaded nls_iso8859-1 snd-pcm-oss snd-pcm-plugin
snd-mixer-oss ipt_REDIRECT ipt_MASQUERADE iptable_mangle iptable_nat
ip_conntrack iptable_filter ip_tables ide-scsi sr_mod sg scsi_mod
parport_pc lp parport ipv6 snd-seq-midi snd-seq-midi-event snd-seq
snd-card-via686a snd-pcm snd-timer snd-ac97-codec snd-mixer
snd-mpu401-uart snd-rawmidi snd-seq-device snd soundcore 3c59x
Please help !
--
Martin Zabadal
http://www.aufeerdesign.cz
reply other threads:[~2002-03-07 16:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C8793AB.5080309@afd.cz \
--to=zabadal@afd.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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