From owner-freebsd-current Thu Nov 28 0:29:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 894EC37B401; Thu, 28 Nov 2002 00:29:15 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC15F43E9C; Thu, 28 Nov 2002 00:29:13 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA26143; Thu, 28 Nov 2002 19:28:46 +1100 Date: Thu, 28 Nov 2002 19:42:25 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Emiel Kollof Cc: current@FreeBSD.ORG, Subject: Re: ext2fs and NFS exporting wackyness In-Reply-To: <20021128064335.GA43060@hackerheaven.org> Message-ID: <20021128193738.V11880-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 28 Nov 2002, Emiel Kollof wrote: > I'm having some odd trouble with exporting a ext2fs with NFS. > ... > Seems allright, no? Well, when I invoke or HUP mountd, the following > happens: > > kernel: ext2fs doesn't support the old mount syscall > mountd[344]: could not remount /storage: Operation not supported > mountd[344]: bad exports list line /home -alldirs -network 10.0.0.0 -mask > 255.255.255.0 > > It _should_ export fine, but the remounting does not work, causing > mountd to think something's amiss and abort my cunning plan to share > data across my network. mountd(8) only uses the old mount syscall (mount(2)), but support for mount(2) in ext2fs was axed in rev.1.97 of ext2_vfsops.c. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message