From: Marc Schmitt Subject: Large export list leads to "Invalid argument" errors when executing 'exportfs -r' Date: 05 Jul 2003 13:44:09 +0200 Sender: nfs-admin@lists.sourceforge.net Message-ID: <1057405449.3361.64.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from medoc.inf.ethz.ch ([129.132.178.200]) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 19YlT3-0005c2-00 for ; Sat, 05 Jul 2003 04:44:37 -0700 Received: from localhost (localhost [127.0.0.1]) by medoc.inf.ethz.ch (Postfix) with ESMTP id 7C5075619C for ; Sat, 5 Jul 2003 13:44:34 +0200 (MEST) Received: from medoc.inf.ethz.ch ([127.0.0.1]) by localhost (medoc [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18357-01-4 for ; Sat, 5 Jul 2003 13:44:33 +0200 (MEST) Received: from [192.168.1.40] (vpn-global-dhcp3-014.ethz.ch [129.132.210.14]) by medoc.inf.ethz.ch (Postfix) with ESMTP id 394D156197 for ; Sat, 5 Jul 2003 13:44:33 +0200 (MEST) To: nfs@lists.sourceforge.net Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: Hi all, I'm using RedHat 7.3 as NFS server, kernel 2.4.18-27.7.xsmp, nfs-utils 1.0.3. For each home directory, we make an entry into /etc/exports of the type: /export/home/ @(rw,sync) The @ netgroups contain usually a whole bunch of machines in FQDN notation. This setup used to work fine, I could add a new entry to /etc/exports and issue 'exportfs -r' and everything would work as expected, the new home could be mounted on the machines in @. Somehow, with /etc/exports growing more and more (currently 137 entries), 'exportfs -r' started giving errors of the type: >:/export/home/: Invalid argument Currently, I get three of those error lines for three entries in /etc/exports. Lokks like it fails when it tries to unexport the entry, 'exportsfs -r -v' shows: unexporting >:/export/home/ from kernel >:/export/home/: Invalid argument I made several tests, even when I delete the line in /etc/exports for , 'exportfs -r' will still give this error. I've deleted the corresponding entry in /var/lib/nfs/xtab but 'exportfs -r' would just add it again, obviously it's cached in the kernel table. Looking at 'showmount -a', I noticed that the server thinks, that has /export/home/ mounted, still. Even though the client does not have the home mounted from the server. I mounted the home on , unmounted and issued 'exportfs -r' on the server and the error message "somehost part of @>:/export/home/: Invalid argument" did not appear again. Interestingly, I have not seen this error message for linux clients. The two machines I have seen it for are: - SunOS 5.9 - IRIX64 6.5 But then I'm seeing this error for a week only, now. The server seems to work fine, though. Even if it reports an error for , can mount the corresponding home. I just wanted to report this issue and will gladly provide more infos if required. Regards, Marc ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs