From: Stephan von Krawczynski <skraw.ml@ithnet.com>
To: linux-kernel@vger.kernel.org
Subject: Path length and filename length linux deficiency
Date: Tue, 31 Mar 2020 23:34:32 +0200 [thread overview]
Message-ID: <20200331233432.372f2f68@ithnet.com> (raw)
Hello all,
today I want to raise a topic that seems to have vanished completely since
decades. It's the length limits of pathnames and filenames. One may wonder why
to jump onto such a seemingly dead horse. But in fact it is not. We are in a
world of continous growth of file services for clouds and other user space
apps. And in this world a friend of mine tried to do something very simple:
copying a file tree ... from a w*ndows file service to a linux server. And
guess what: it does not work out.
And the simple reason: the maximum path length in w*ndows systems is 32767,
whereas linux (and POSIX) talk of a maximum of 4096 bytes. It is obvious then
that linux is effectivly unable to hold a deep tree - whereas w*ndows can.
Since I do know for sure it does not work, what are the true reasons?
How can we completely drop these limits in linux (using a capable fs of
course)?
I already asked the samba list and was confirmed that the problem is known and
that there is no easy solution for it.
--
Regards,
Stephan
reply other threads:[~2020-03-31 21:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200331233432.372f2f68@ithnet.com \
--to=skraw.ml@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.