[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Findutils-patches] [PATCH] find memory leak

From: Goffredo Baroncelli
Subject: Re: [Findutils-patches] [PATCH] find memory leak
Date: Sun, 12 Feb 2017 13:25:05 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0

On 2017-02-10 23:21, Dale R. Worley wrote:
> Goffredo Baroncelli <address@hidden> writes:
>>> Or perhaps the inode
>>> returned in stat() could contain a field to contain the snapshot
>>> identifier along with the "base" i-node number.  (I guess we know the
>>> snapshot identifiers don't exceed 255!)
>> A bit more: ~2^64 ...
>> However it is suggested to not make more of few hundreds....
> Isn't the snapshot identifier currently mapped to the minor device
> number?  And aren't those limited to 8 bits?

No, they have a uint64 as identifier....
In mailing list some suggested to not make more than 300 snapshots in order to 
avoid bad performance. But this limit is doable.

Anyway, in 32 bit mode, the inode is 32 bit too. So leaving only 24 bit for the 
file inode means that you cannot have more than 24millions of files. I not sure 
that this limits would be acceptable today.

> Dale

gpg Goffredo Baroncelli <>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D  17B2 0EDA 9B37 8B82 E0B5

reply via email to

[Prev in Thread] Current Thread [Next in Thread]