From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 14:22:05 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 37BC41AA for ; Wed, 21 Jan 2015 14:22:05 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B99E3901 for ; Wed, 21 Jan 2015 14:22:04 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id em10so15215239wid.1 for ; Wed, 21 Jan 2015 06:22:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=aRET4FQiqXni17gLtJvyeHBdvX+XrtP2FTah7Ri1RSI=; b=RiGJsiqWUM73Q9P+SP+QvJp0DJwBaEXKKywqC7j5fx3xMKyx7I/AZ8JNizqrRKQcio eLl/6J62LyhRToXao55e+R3Xy9hu0p2c6Eq5qLnOZEmDL7ADsUl0QoUXA7h7ebX7GNeD DHWQf0Q5rEuajwRavGdjqmKetKQ2lpOxmI3UZ/DuUS0+BTx54UCieGLYLfTqC2hcSGtv NcbNJb4I6aGlcv6X2yJZDC4qojNBjEkcazvSk0+4OGUMXA2Q+4VX0Bugvnq9/xqb2vZn HdRA0YMFSMazGE20nJUpwQo4ty42B/xDR9kX53WEHtK2M5pbk0qbRytmbQcGrvFChNVX 9u9A== X-Received: by 10.180.207.211 with SMTP id ly19mr57596738wic.73.1421850122559; Wed, 21 Jan 2015 06:22:02 -0800 (PST) Received: from MARC-THINKPAD.queenland (AOrleans-656-1-23-170.w90-20.abo.wanadoo.fr. [90.20.238.170]) by mx.google.com with ESMTPSA id hz9sm25731507wjb.17.2015.01.21.06.22.01 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Wed, 21 Jan 2015 06:22:01 -0800 (PST) Date: Wed, 21 Jan 2015 15:22:00 +0100 From: =?UTF-8?B?TcOkcms=?= Owen Cc: freebsd-stable@freebsd.org Subject: Re: NFS "mount system call failed" Message-ID: <20150121152200.707d6361@MARC-THINKPAD.queenland> In-Reply-To: <2096124637.17646377.1421796855627.JavaMail.root@uoguelph.ca> References: <20150120164409.49403c6e@MARC-THINKPAD.queenland> <2096124637.17646377.1421796855627.JavaMail.root@uoguelph.ca> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2015 14:22:05 -0000 On Tue, 20 Jan 2015 18:34:15 -0500 (EST) Rick Macklem wrote: > Mark Owen wrote: > > Hi everyone, > > > > I'm using FreeBSD 10.1 to share a ZFS pool (mounted at > > /media/storage) > > through NFS to Linux clients (Debian 7). I don't seem to get any > > errors > > when the nfs services start on FreeBSD but I can't mount the shares > > on > > the clients, all I get is: mount.nfs4: mount system call failed > > (Tried > > as NFSv3 and NFSv4, same result). > > > > I'm really frustrated here since It worked barely an hour ago and I > > have absolutely no idea why I getting this error now. > > > Well, here's a couple of comments: > 1 - Look in /var/log/messages for any errors generated by mountd or > nfsd on the FreeBSD server. > 2 - Make sure the daemons (mountd and nfsd) are running, via "ps > axHl". 3 - It appears you have exported the file system "read-only", > but are trying to mount it read/write. (I'm not sure this would > produce an error at mount time or just if/when the client tries to > write to the file server?) > 4 - If nothing above helps, use "tcpdump -s 0 -w xxx.pcap host > " on the server to capture packets during a mount > attempt and then look at xxx.pcap in wireshark (since it understands > NFS). This will show you what interaction is going on between > client<->server and may give you the hint as to what is broken. > > rick > > > Anyway, here are my /etc/rc.conf and /etc/exports files from the > > server: > > > > /etc/rc.conf > > ... > > ## ZFS > > zfs_enable="YES" > > ## NFSv4 Server > > nfs_server_enable="YES" > > nfsv4_server_enable="YES" > > rpcbind_enable="YES" > > mountd_enable="YES" > > mountd_flags="-r" > > #rpc_lockd_enable="YES" > > #rpc_statd_enable="YES" > > > > /etc/exports (I tried both as NFSv3 and NFSv4, here are the two > > options) > > -NFSv3: > > /media/storage/data -ro -alldirs -network 192.168.1.0 -mask > > 255.255.255.0 > > > > -NFSv4: > > V4:/media/storage -network 192.168.1.0 -mask 255.255.255.0 > > /media/storage/data -ro -alldirs -network 192.168.1.0 -mask > > 255.255.255.0 > > > > > > On the clients I use the following commands to try to mount the > > share: > > - NFSv3: mount -t nfs -o nolock server-ip:/media/storage/data > > /mnt/tmp > > - NFSv4: mount -t nfs4 server-ip:/data /mnt/tmp > > > > Thank you for reading and I hope that someone will be able to help > > me. > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to > > "freebsd-stable-unsubscribe@freebsd.org" > >