From: Maxim Blinov <maxim.blinov@embecosm.com>
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>
Subject: Re: Help! How to delete an 8094-byte PATH?
Date: Thu, 27 Jan 2022 15:09:21 +0000 [thread overview]
Message-ID: <a57e2fde-f430-952d-9878-d7a5307cb2db@embecosm.com> (raw)
In-Reply-To: <YfKg3DQS0h2lPo3z@casper.infradead.org>
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
next prev parent reply other threads:[~2022-01-27 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 7:06 Help! How to delete an 8094-byte PATH? Maxim Blinov
2022-01-27 7:27 ` Maxim Blinov
2022-01-27 12:20 ` Ritesh Harjani
2022-01-27 13:40 ` Matthew Wilcox
2022-01-27 15:09 ` Maxim Blinov [this message]
2022-01-27 15:34 ` Maxim Blinov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a57e2fde-f430-952d-9878-d7a5307cb2db@embecosm.com \
--to=maxim.blinov@embecosm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=riteshh@linux.ibm.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox