Date:   Tue, 16 Nov 2021 17:52:55 +0000 (GMT)
From:   Mark Hills <mark@xwax.org>
To:     Andreas Dilger <adilger@dilger.ca>
cc:     Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: Maildir quickly hitting max htree
In-Reply-To: <82C9B126-527B-4D41-8E01-84C560E06A3F@dilger.ca>
Message-ID: <2111161748390.26337@stax.localdomain>
References: <d1f5c468-4afa-accc-7843-83b484dc081@xwax.org> <82C9B126-527B-4D41-8E01-84C560E06A3F@dilger.ca>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="-1463793916-1319953200-1637085175=:26337"
Precedence: bulk

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---1463793916-1319953200-1637085175=:26337
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Sat, 13 Nov 2021, Andreas Dilger wrote:

> >>> On Nov 12, 2021, at 11:37, Mark Hills <mark@xwax.org> wrote:
> >>>=20
> >>> =EF=BB=BFSurprised to hit a limit when handling a modest Maildir case=
; does=20
> >>> this reflect a bug?
> >>>=20
> >>> rsync'ing to a new mail server, after fewer than 100,000 files there=
=20
> >>> are intermittent failures:
> >>=20
> >> This is probably because you are using 1KB blocksize instead of 4KB,=
=20
[...]
> > Is block size the only factor? If so, a patch like below (untested) cou=
ld=20
> > make it clear it's relevant, and saved the question in this case.
>=20
> The patch looks reasonable, but should be submitted separately with
> [patch] in the subject so that it will not be lost. =20
>=20
> You can also add on your patch:
>=20
> Reviewed-by: Andreas Dilger <adilger@dilger.ca>

Thanks. When I get a moment I'll aim to test the patch and submit=20
properly.

--=20
Mark
---1463793916-1319953200-1637085175=:26337--