On 7/4/2016 12:48 PM, Stephan Wiesand wrote:
>
> On Jul 4, 2016, at 16:27 , Jeffrey Altman wrote:
>
>> The directory size restrictions are one of the reasons that /afs cannot
>> be used for a large number of applications. The AuriStor File System
>> implements a new directory format which is
On Jul 4, 2016, at 16:27 , Jeffrey Altman wrote:
> The directory size restrictions are one of the reasons that /afs cannot
> be used for a large number of applications. The AuriStor File System
> implements a new directory format which is understood only by AuriStor
> clients. This format
On 7/4/2016 11:57 AM, Matthew Lowy wrote:
> Hi Jeffrey,
>
> a locale where double-byte characters were in file names the packing wouldn't
> be as good.
All AFS3 directory entries are stored as single byte C-strings. Unicode
names as stored by Windows, OSX, Linux with the UTF8 locale, etc store
ct: Re: [OpenAFS] Number of files in an OpenAFS volume...
On 7/4/2016 6:55 AM, Matthew Lowy wrote:
> Hello,
>
> We have a number of OpenAFS volumes that serve as storage for (public)
> mirrors and one of them is misbehaving when updated from upstream - the
> error indicates we've reached th
On 7/4/2016 6:55 AM, Matthew Lowy wrote:
> Hello,
>
> We have a number of OpenAFS volumes that serve as storage for (public)
> mirrors and one of them is misbehaving when updated from upstream - the
> error indicates we've reached the limit of file names allowed in a volume.
In a volume or a
Hello,
We have a number of OpenAFS volumes that serve as storage for (public) mirrors
and one of them is misbehaving when updated from upstream - the error indicates
we've reached the limit of file names allowed in a volume.
The limit I am seeing is not compatible with my understanding of how
