From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
Subject: Re: Fwd: Undelivered Mail Returned to Sender
Date: Sat, 22 Oct 2022 14:10:59 +0200 [thread overview]
Message-ID: <Y1Pd0xX15IWe01qW@wildebeest.org> (raw)
In-Reply-To: <c345431d-035e-1be2-36a1-4292b31b983b@foss.st.com>
Hi Torbjorn,
On Sat, Oct 22, 2022 at 10:37:05AM +0200, Torbjorn SVENSSON via Overseers wrote:
> On 2022-10-21 21:45, Frank Ch. Eigler wrote:
> > > FYI, it looks like there is an issue with the mail system at sourceware.org
> > > (maybe this mail wont be delivered either...).
> >
> > Thanks, we tweaked two related things, pls let us know if this reoccurs.
>
> I just noticed another failure (attached), identical to the one yesterday.
Seems like gdb-patches is just a little bit too big and some resource
constrainst still kick in (it also looks like the last issue caused
the search database to get corrupted).
I'll reimport gdb-patches into public-inbox for just the last 12 years
(currently it contains everything since 1997). That should keep the
size of the git packs, indexes and search database under control.
Note that this error just means that the message wasn't properly
imported into public-inbox at inbox.sourceware.org. The message was
still delivered to the list. Still annoying of course.
Sorry for the inconvenience.
Cheers,
Mark
next prev parent reply other threads:[~2022-10-22 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221021191325.9FEBD3856DC0@sourceware.org>
2022-10-21 19:17 ` Torbjorn SVENSSON
2022-10-21 19:45 ` Frank Ch. Eigler
2022-10-22 8:37 ` Torbjorn SVENSSON
2022-10-22 12:10 ` Mark Wielaard [this message]
[not found] <20210723021455.EB1621C3318@fx303.security-mail.net>
2021-07-23 2:33 ` Brian Inglis
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=Y1Pd0xX15IWe01qW@wildebeest.org \
--to=mark@klomp.org \
--cc=fche@redhat.com \
--cc=overseers@sourceware.org \
--cc=torbjorn.svensson@foss.st.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).