On Mon, Sep 12, 2016 at 11:00 AM, Ilya Moldovan wrote:
> Thanks, John
>
> But why listing files in a directory with about a million files takes
> about 30 minutes?
Unless you've enabled experimental features, you're trying to read in
a single 1-million-inode directory object — and it sounds like
Are you running ‘ls’ or are you doing something like: 'getfattr -d -m
ceph.dir.* /path/to/your/ceph/mount’ ?
—Lincoln
> On Sep 12, 2016, at 1:00 PM, Ilya Moldovan wrote:
>
> Thanks, John
>
> But why listing files in a directory with about a million files takes
> about 30 minutes?
>
> Ilya Mo
Thanks, John
But why listing files in a directory with about a million files takes
about 30 minutes?
Ilya Moldovan
2016-09-08 20:59 GMT+03:00, Ilya Moldovan :
> Hello!
>
> How CephFS calculates the directory size? As I know there is two
> implementations:
>
> 1. Recursive directory traversal lik
On Thu, Sep 8, 2016 at 6:59 PM, Ilya Moldovan wrote:
> Hello!
>
> How CephFS calculates the directory size? As I know there is two
> implementations:
>
> 1. Recursive directory traversal like in EXT4 and NTFS
> 2. Calculation of the directory size by the file system driver and save it
> as an attr
Hello!
How CephFS calculates the directory size? As I know there is two
implementations:
1. Recursive directory traversal like in EXT4 and NTFS
2. Calculation of the directory size by the file system driver and save it
as an attribute. In this case, the driver catches adding, deleting and
editing
