From: =?iso-8859-1?Q?Bj=F6rn?= JACKE Subject: Re: size limit of extended attributes Date: Thu, 30 Apr 2015 18:06:22 +0200 Message-ID: References: <55424038.7000109@plexistor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Trond Myklebust , Linux FS-devel Mailing List To: Boaz Harrosh Return-path: Received: from mail1.SerNet.de ([193.175.80.2]:58496 "EHLO mail.SerNet.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750854AbbD3QHO (ORCPT ); Thu, 30 Apr 2015 12:07:14 -0400 Content-Disposition: inline In-Reply-To: <55424038.7000109@plexistor.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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 pob= lished > 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__ dir= ectory >=20 > 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. Apart fro= m the fact that the meta data is detached from the file, which also makes thi= s 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 fo= r the Linux kernel. Bj=C3=B6rn --=20 SerNet GmbH, Bahnhofsallee 1b, 37081 G=C3=B6ttingen =E2=98=8E +49-551-370000-0, =E2=84=BB +49-551-370000-9 AG G=C3=B6ttingen, HRB 2816, GF: Dr. Johannes Loxen -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html