| To: | Chris Walker <christopher.walker@xxxxxxxxx> |
|---|---|
| Subject: | Re: quick question about filename length |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Sat, 16 May 2009 16:25:11 -0400 |
| Cc: | Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <554e24be0905161106x6a62b7bldc65325ac4102628@xxxxxxxxxxxxxx> |
| References: | <554e24be0905160915l49ff901bn41e4332349c555bc@xxxxxxxxxxxxxx> <4A0EF228.3010702@xxxxxxxxxxx> <554e24be0905161106x6a62b7bldc65325ac4102628@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
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? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_repair after reboot refuse repair my filesystem, Eric Sandeen |
|---|---|
| Next by Date: | Re: [PATCH] xfsprogs: fix readline/editline for xfs_io and xfs_quota, Christoph Hellwig |
| Previous by Thread: | Re: quick question about filename length, Chris Walker |
| Next by Thread: | Re: quick question about filename length, Martin Steigerwald |
| Indexes: | [Date] [Thread] [Top] [All Lists] |