On 04/30/2015 07:06 PM, Björn JACKE wrote: > On 2015-04-30 at 17:46 +0300 Boaz Harrosh sent off: >> The hacks need not be so ugly and they can be well documented and poblished >> as a public STD. >> ./foo-with-streams (With xatters info) >> ./.foo-with-streams.__STREAMES__/ (backpointer xattrs-info) >> ./.foo-with-streams.__STREAMES__/SA >> ./.foo-with-streams.__STREAMES__/SB >> ... >> And some special mod bits on the .foo-with-streams.__STREAMES__ directory >> >> The smb read-dir parser removes those hidden directories > > any hack like this would mean that for long file names which are close NAME_MAX > this will not work. Yes, such long file names are being used. > Solvable use the infamous ....xxxx~1 encoding solution for the dirs > Apart from the > fact that the meta data is detached from the file, which also makes this > workaround quite sub-optimal. Still the only real solution I see would be > bigger EA sizes. I was hoping that this would be not a big challenge for the > Linux kernel. > Again you are ignoring my point. If the FS would like to (easily) keep these xattrs for you, you have a POSIX API problem. You will need an alternate API to be able to read/write these big xattrs in chunks. It might be possible to make that 64K say 2M but you need a CONST-MAX size. with current API, is there a number that will satisfy you? > Björn > Cheers Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
