Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
To:     Matthew Wilcox <willy@infradead.org>,
        Ritesh Harjani <riteshh@linux.ibm.com>
Cc:     linux-ext4@vger.kernel.org,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>
References: <d4a67b38-3026-59be-06a8-3a9a5f908eb4@embecosm.com>
 <20220127122039.45kxmnm3s7kflo6h@riteshh-domain>
 <YfKg3DQS0h2lPo3z@casper.infradead.org>
From:   Maxim Blinov <maxim.blinov@embecosm.com>
Subject: Re: Help! How to delete an 8094-byte PATH?
Message-ID: <a57e2fde-f430-952d-9878-d7a5307cb2db@embecosm.com>
Date:   Thu, 27 Jan 2022 15:09:21 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <YfKg3DQS0h2lPo3z@casper.infradead.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi Matthew, Ritesh,

On 27/01/2022 13:40, Matthew Wilcox wrote:
> here's an idea:
> 
> while true; do
> 	mv confdir3/confdir3 tmpd; rmdir confdir3; mv tmpd confdir3;
> done
> 

Thankyou for all your comments - mv'ing a child directory "up" and
deleting *that* did the trick!

Infact I was complaining about this to some colleagues who kindly
pointed me to this thread [1] where someone has exactly the same issue.

Searching for `confdir3`, it turns out this issue is more googleable
than I initially realized - there's quite a few others who have bumped
into these weird path length limitations, in particular with docker
(there's another thing I forgot to mention - to be clear, I'm running
QEMU inside a docker container.)

Still it seems strange, since the QEMU VM disk image is a static file
within the docker file system, and there are no bind mounts going on in
the container.

[1]: https://github.com/moby/moby/issues/13451