All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Tue, 16 Nov 2021 17:52:55 +0000 (GMT)	[thread overview]
Message-ID: <2111161748390.26337@stax.localdomain> (raw)
In-Reply-To: <82C9B126-527B-4D41-8E01-84C560E06A3F@dilger.ca>

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

On Sat, 13 Nov 2021, Andreas Dilger wrote:

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

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

-- 
Mark

  reply	other threads:[~2021-11-16 17:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 19:52 Maildir quickly hitting max htree Mark Hills
     [not found] ` <36FABD31-B636-4D94-B14D-93F3D2B4C148@dilger.ca>
2021-11-13 12:05   ` Mark Hills
2021-11-13 17:19     ` Andreas Dilger
2021-11-16 17:52       ` Mark Hills [this message]
2021-11-14 17:44     ` Theodore Ts'o
2021-11-16 19:31       ` Mark Hills
2021-11-17  5:20         ` Theodore Ts'o
2021-11-17 13:13           ` Mark Hills

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=2111161748390.26337@stax.localdomain \
    --to=mark@xwax.org \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.