public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 217145] Feature request: I need very long directory and file names
Date: Mon, 06 Mar 2023 10:15:25 +0000	[thread overview]
Message-ID: <bug-217145-13602-xUjOe0PCqO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217145-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217145

Christian Kujau (kernel@nerdbynature.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kernel@nerdbynature.de

--- Comment #1 from Christian Kujau (kernel@nerdbynature.de) ---
Ext4 (and Btrfs and XFS too) supports file names up to 255 bytes long. How long
do you need a file name to be? That 1-3 KB refers to....a list of files, or the
actual file name length? I'm interested in the actual use cases for this. Also,
what's that name of the torrent client that magically truncates file names
here?

$ mkdir -p $(perl -e 'print "a"x255')/$(perl -e 'print "b"x255')
$ touch $(perl -e 'print "a"x255')/$(perl -e 'print "b"x255')/$(perl -e 'print
"c"x255')
$ find a*
aaaaaaaaaaaaa[...] well, you get the idea :-)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2023-03-06 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06  8:08 [Bug 217145] New: Feature request: I need very long directory and file names bugzilla-daemon
2023-03-06 10:15 ` bugzilla-daemon [this message]
2023-03-06 13:00 ` [Bug 217145] " bugzilla-daemon
2023-03-06 16:05 ` bugzilla-daemon
2023-03-06 18:38 ` bugzilla-daemon
2023-03-08  5:01 ` bugzilla-daemon

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=bug-217145-13602-xUjOe0PCqO@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox