From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Martin Sebor <msebor@gmail.com>, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Bugzilla timing out
Date: Mon, 15 Jan 2018 22:29:00 -0000 [thread overview]
Message-ID: <CAMe9rOoPZTm6mYGgPcxRewb+o3w1Brcpjm1+BKDJSjWhHjQKnA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1801152056340.9834@digraph.polyomino.org.uk>
On Mon, Jan 15, 2018 at 12:58 PM, Joseph Myers <joseph@codesourcery.com> wrote:
> On Mon, 15 Jan 2018, Martin Sebor wrote:
>
>> I'm having trouble bringing up bugs or updating them. Has
>> anyone else noticed Bugzilla (and/or other services running
>> on gcc.gnu.org) being very slow or timing out?
>
> I'm presuming this comes from the read errors on sdi that I just reported
> to overseers (if reads keep having to fail / time out before the RAID
> gives up on sdi and reads the data from another disk in the RAID instead).
>
> [710507.350074] sd 0:2:8:0: [sdi] CDB: Read(10): 28 00 07 e0 1c 50 00 00 08 00
> [710507.350301] end_request: I/O error, dev sdi, sector 132127824
> [710507.529984] md/raid:md3: read error corrected (8 sectors at 132125776 on sdi1)
> [710507.530346] md/raid:md3: read error corrected (8 sectors at 132125784 on sdi1)
> [710507.530704] md/raid:md3: read error corrected (8 sectors at 132125792 on sdi1)
>
It took a long time to do "svn ci".
--
H.J.
next prev parent reply other threads:[~2018-01-15 22:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 20:54 Martin Sebor
2018-01-15 20:58 ` Joseph Myers
2018-01-15 22:29 ` H.J. Lu [this message]
2018-01-18 19:11 ` Frank Ch. Eigler
2018-01-21 6:20 ` Eric Gallager
2018-01-22 18:09 ` Frank Ch. Eigler
2018-01-23 10:26 ` Richard Biener
2018-01-23 13:19 ` Frank Ch. Eigler
2018-01-26 21:52 ` Martin Sebor
2018-01-26 21:55 ` H.J. Lu
2018-01-26 22:04 ` Frank Ch. Eigler
2018-01-26 22:15 ` Joseph Myers
2018-01-26 23:08 ` Frank Ch. Eigler
2018-01-26 23:29 ` Martin Sebor
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=CAMe9rOoPZTm6mYGgPcxRewb+o3w1Brcpjm1+BKDJSjWhHjQKnA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=msebor@gmail.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).