From owner-freebsd-questions@FreeBSD.ORG Mon Feb 16 13:27:09 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 978684E2 for ; Mon, 16 Feb 2015 13:27:09 +0000 (UTC) Received: from server949-han.de-nserver.de (server949-han.de-nserver.de [77.75.250.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F1C5E85A for ; Mon, 16 Feb 2015 13:27:07 +0000 (UTC) Received: (qmail 29076 invoked from network); 16 Feb 2015 14:26:58 +0100 X-Fcrdns: Yes Received: from dslb-094-218-010-244.094.218.pools.vodafone-ip.de (HELO midgard.local) (94.218.10.244) (smtp-auth username konstantin@schukraft.org, mechanism plain) by server949-han.de-nserver.de (qpsmtpd/0.92) with (ECDHE-RSA-AES256-SHA encrypted) ESMTPSA; Mon, 16 Feb 2015 14:26:58 +0100 Message-ID: <54E1F020.8040107@schukraft.org> Date: Mon, 16 Feb 2015 14:26:56 +0100 From: Konstantin Schukraft User-Agent: "" MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: current status RE: "File name too long" issues Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-User-Auth: Auth by konstantin@schukraft.org through 94.218.10.244 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2015 13:27:09 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, this seems a rather old issue that's still alive, manifesting in NFS mounts, nullfs mounts with jails, etc: "Overly" long path names in these situations result in an error like "mount_nullfs: : File name too long". I, for example, run into this every time I try to setup a poudriere jail, others seem too. Since the forums didn't really provide an answer, I'll ask here: Is there work currently being done on this issue? Because this reply: https://docs.freebsd.org/cgi/getmsg.cgi?fetch=210593+0+/usr/local/www/db/text/2014/freebsd-questions/20141221.freebsd-questions seems to indicate this has been fixed, which definitely isn't the case for many people, including myself. So what's the status on that? Am I overlooking something important? Thank you, Konstantin -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJU4fAdAAoJEH3raMNeVmMF1rgP/jUrM0Lqx7CCZ4qEa8d7zb2b vbj433dVWcJiVyATsQarqO8dum8Unv2UisUeiyukc/j1DtagXIzEe34zH+S9vvD0 Jy/K4Bdz75mzGQLt2kbexEqVxdXk4Xf7kymAjgFkx3gb1h+7o4/OcmJflEBJnwz0 bxBlVM5Xu0F4VNwfUL8owfQRBcyjtP4iHBxY19Qobm8fGs7sDOpwi5mriZXgr4RH 4VHI/gtRacf0RVVLKGgSxLrHUOD4oCuEM345aBHSUyp+yPRIRzkAfC90EdNkUTLO +QntlGKW0By4A0xvIJroRH28XMOwCt7fnDf3UK41CKqghR56xdwb4WvrNW/HDbJz /Ns6fcR9IkeZiYxU9IubrX9r78ZnPu7XdtVdqFkndBD4jb0/jq3PKFNQTXtQ0cyn cMYOykkY6wfg4m+evYFJggfsSdnFsTq3TDeQPYglByHEiM5tMFrVbSdz21HcGOJL Y5U7cT/nY3aUJ8Z6o1I9vFgCwj5HuT6Gq38bQXfMthspeeRII4jvXRAfPhFWxWBn vqSb/djATBEzg51Xf8jr7hx++BXkj2adYATd+eUBAvuNWZYkDDdfBlCqTDTr0tmQ DhUvOvdedtiiDKQM0zeLMzQWg44QhznJlmfQLW9iQ4B9WvfaYDR+ZN+3lSMvzOmY NgGfElzi2CFBF+in/HV5 =pgRh -----END PGP SIGNATURE-----