[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/2] fts: introduce the FTS_NOLEAF flag
|
From: |
Pádraig Brady |
|
Subject: |
Re: [PATCH 1/2] fts: introduce the FTS_NOLEAF flag |
|
Date: |
Mon, 18 Jan 2016 17:33:54 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 |
On 18/01/16 16:25, Pádraig Brady wrote:
> On 18/01/16 16:10, Kamil Dudka wrote:
>> On Monday 21 December 2015 15:01:56 Kamil Dudka wrote:
>>> On Monday 21 December 2015 00:05:51 Pádraig Brady wrote:
>>>> On the other hand we've had no reports of issues with the
>>>> existing auto config done by FTS.
>>>
>>> Because the leaf optimization has been enabled for reiserfs only until now.
>>> I suspect that NFS will not be that easy and such file system issues might
>>> be difficult to debug without the -noleaf option actually implemented.
>>
>> So we have the first bug report about the leaf optimization causing problems
>> to users of find(1):
>>
>> https://bugzilla.redhat.com/1299169
>>
>> Is this a reason to implement the -noleaf option of find (and consequently
>> the FTS_NOLEAF flag of gnulib's FTS)?
>
> Maybe. But I'm also thinking it might mean we
> can't enable this optimization for NFS
> as the implementations are too disparate in this regard?
>
> It seems prudent for example to disable this
> optimization for the imminent coreutils 8.25 release :(
Patch attaced
nfs-noleaf.patch
Description: Text Data