From owner-freebsd-stable Sat Jan 20 14:41: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3C727.dip.t-dialin.net [62.227.199.39]) by hub.freebsd.org (Postfix) with ESMTP id 0AF6237B402 for ; Sat, 20 Jan 2001 14:40:37 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id A7F41A2002; Sat, 20 Jan 2001 23:40:24 +0100 (CET) Date: Sat, 20 Jan 2001 23:40:24 +0100 From: Matthias Andree To: Linux NFS mailing list , reiserfs-list@namesys.com, FreeBSD Stable Subject: Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, ReiserFS Message-ID: <20010120234024.A1771@emma1.emma.line.org> Mail-Followup-To: Linux NFS mailing list , reiserfs-list@namesys.com, FreeBSD Stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have troubles mounting a reiserfs (3.5.29) file system that is on a Linux 2.2.18 nfsv3 server with a FreeBSD 4.2-STABLE client, I'm getting bogus "read-only file system" errors even on just ls. If I mount the same system via NFS v2, everything goes smooth. If mount an ext2 file system from the same server on the same client, everything goes smooth, regardless if using NFS v3 (default) or v2 (mount_nfs -2). If I use a Solaris 7 or Linux client for mounting, everything goes smooth. I'm not quite sure if it's a Linux or a FreeBSD bug, and if Linux, if it's NFS-specific or reiserfs specific. There seem to be issues with NFS v3 serving reiserfs still. If you need further information (traced syscalls, more elicit network dump), please let me know. Here's a tcpdump 3.5 excerpt, the first two lines still from mount, the other ones from ls /mnt (not showing portmapper and mountd packets, there are unspectacular): 23:22:29.528242 freebsd.526363636 > emma1.nfs: 144 access fh 0,1/2 003f (ttl 64, id 44190) 23:22:29.528764 emma1.nfs > freebsd.526363636: reply ok 116 access ERROR: Read-only file system (ttl 64, id 12889) 23:22:31.516945 freebsd.526363637 > emma1.nfs: 144 access fh 0,1/2 003f (ttl 64, id 44202) 23:22:31.517484 emma1.nfs > freebsd.526363637: reply ok 116 access ERROR: Read-only file system (ttl 64, id 12907) Here's a tcpdump of a successful NFS v2 mount: 23:22:54.615412 freebsd.526363639 > emma1.nfs: 136 getattr fh 0,1/2 (ttl 64, id 44300) 23:22:54.615894 emma1.nfs > freebsd.526363639: reply ok 96 getattr DIR 41777 ids 0/0 sz 706 (ttl 64, id 13070) Here of a successful NFS v3 ext2 mount: 23:29:05.976285 freebsd.526363641 > emma1.nfs: 144 access fh Unknown/1 003f (ttl 64, id 44492) 23:29:05.976823 emma1.nfs > freebsd.526363641: reply ok 120 access attr: DIR 40755 ids 0/0 sz 1024 nlink 13 rdev 0/0 fsid 0 nodeid 0 a/m/ctime 980028529.000000 979555088.000000 979555088.000000 c 0003 (ttl 64, id 13585) -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message