Date: Fri, 8 Sep 2017 10:32:17 -0700 From: Conrad Meyer <cem@freebsd.org> To: David Wolfskill <david@catwhisker.org>, Julian Elischer <julian@freebsd.org>, freebsd-current <freebsd-current@freebsd.org>, Rick Macklem <rmacklem@uoguelph.ca> Subject: Re: extending the maximum filename length Message-ID: <CAG6CVpUCVzOvqOHP=3jLOL8GEzHcqQG0O-SATMe4QLZD35FykQ@mail.gmail.com> In-Reply-To: <20170908172125.GB1152@albert.catwhisker.org> References: <0154558d-b2ad-af97-3960-3e392678f709@freebsd.org> <20170908172125.GB1152@albert.catwhisker.org>
index | next in thread | previous in thread | raw e-mail
On Fri, Sep 8, 2017 at 10:21 AM, David Wolfskill <david@catwhisker.org> wrote: > On Sat, Sep 09, 2017 at 01:15:31AM +0800, Julian Elischer wrote: >> Has anyone using freeBSD ever increased NAME_MAX (filename maximum >> length) and have any experience with it? >> >> We ($JOB) would recompile the entire system so intra-system >> compatibility would probably be ok, and we have our own filesystem >> which would support it. >> >> But I wonder if anyone has tried it and hit unexpected problems. >> .... > > Not *strictly* a "filename length" issue, but one thing I (think > I) recall encountering a while back was an (88-character?) upper > limit on the length of the full pathname of a mount point. > > So that could prove ... annoying (if I actually recall correctly, > and the situation has not changed since). Hi David, I think mountpoint name length is largely an orthogonal issue. Fortunately, the 88 character limit (MNAMELEN) was already addressed recently (bumped to 1024) with the ino64 project. Best, Conradhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpUCVzOvqOHP=3jLOL8GEzHcqQG0O-SATMe4QLZD35FykQ>