From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@sandeen.net>,
Chris Walker <christopher.walker@gmail.com>
Subject: Re: quick question about filename length
Date: Sat, 16 May 2009 23:42:19 +0200 [thread overview]
Message-ID: <200905162342.19915.Martin@lichtvoll.de> (raw)
In-Reply-To: <20090516202511.GA28186@infradead.org>
Am Samstag 16 Mai 2009 schrieb Christoph Hellwig:
> On Sat, May 16, 2009 at 02:06:22PM -0400, Chris Walker wrote:
> > Thanks for you quick reply, Eric.
> >
> > I have a user who is having filenames (path+filename) cut off at 255
> > characters midway through a simulation -- but the problem must be
> > elsewhere
>
> XFS doesn't actually see the whole filename in normal operation (except
> for copying out the data out of symbolic links), as the resolution to
> individual components is done by the VFS. Long file name should work
> just fine on Linux and do in my test. Maybe some buffer is sized using
> incorrect in userspace?
And while a link name itself also can't be longer than about 256
characters (I only tested 250 and 260), a link can point to a longer
path ;-):
martin@shambhala:~/Zeit> mkdir -p
$(ruby -e 'puts "1234567890"*25')/$(ruby -e 'puts "1234567890"*25')
martin@shambhala:~/Zeit> ln -s
$(ruby -e 'puts "1234567890"*25')/$(ruby -e 'puts "1234567890"*25')
testlink
martin@shambhala:~/Zeit> ls -l testlink
lrwxrwxrwx 1 martin martin 501 16. Mai 23:40 testlink ->
12345678901234567890123456789012345678901234567890123456789[...]
martin@shambhala:~/Zeit> (df -hT . | grep -q xfs) && echo "Is XFS"
Is XFS
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-05-16 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 16:15 quick question about filename length Chris Walker
2009-05-16 17:04 ` Eric Sandeen
2009-05-16 18:06 ` Chris Walker
2009-05-16 20:25 ` Christoph Hellwig
2009-05-16 21:42 ` Martin Steigerwald [this message]
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=200905162342.19915.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=christopher.walker@gmail.com \
--cc=hch@infradead.org \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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