From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bell-labs website and plan9
Date: Mon, 9 Apr 2007 12:23:40 -0400 [thread overview]
Message-ID: <a0b4fdc70c9531ba9a41193c219915fe@coraid.com> (raw)
On Mon Apr 9 11:50:41 EDT 2007, rsc@swtch.com wrote:
> erik:
> > i have also noticed that replica/applylog has a problem. when i started
> > experimenting with copying history from our old fileserver to the new
> > one, i started using replica/updatedb and replica/applylog. updatedb
> > worked very well, but applylog hung for me pretty consistantly.
>
> Did you ever use acid to get a stack trace from the `hung' applylogs?
> The only threading in applylog is an implementation of something
> like fcp to copy files using multiple outstanding 9P read requests.
> Since no one else seems to have had problems, I would guess that
> there were just some requests that made your file server thrash.
> But stack traces would make the answer very clear.
i apologize for not having a backtrace, they looked uninformative at the
time. what i rememer was that applylog was not doing any i/o at the time.
(unless it was reading the same blocks over and over.)
in once instance, applylog had the same /proc/$pid/fd for 4 hrs
and generated no system load at all. the
one problem i do see that was not my case (i was working on two successive
days from the dump) is that there is no maximum number
of tries to keep a file from changing underfoot. a log file competing with
a slow link could be problematic.
restarting it where it left off (with an initial line number) generally
fixed the problem. i didn't mention it at the time because i
didn't get to the bottom of the problem.
i'll try to recreate the problem with a backtrace, but anyone else is welcome
to beat me to it.
- erik
next reply other threads:[~2007-04-09 16:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 16:23 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-09 15:32 erik quanstrom
2007-04-09 15:44 ` Devon H. O'Dell
2007-04-09 16:15 ` Martin Neubauer
2007-04-05 19:45 pedro henrique antunes de oliveira
2007-04-05 21:15 ` John Floren
2007-04-05 21:56 ` W B Hacker
2007-04-05 21:57 ` geoff
2007-04-09 14:24 ` Benn Newman
2007-04-09 14:50 ` Devon H. O'Dell
2007-04-09 14:55 ` erik quanstrom
2007-04-09 15:08 ` Devon H. O'Dell
2007-04-09 15:24 ` erik quanstrom
2007-04-09 15:40 ` Devon H. O'Dell
2007-04-09 15:01 ` Devon H. O'Dell
2007-04-09 15:22 ` ron minnich
2007-04-09 15:30 ` Devon H. O'Dell
2007-04-09 18:02 ` ron minnich
2007-04-09 18:11 ` geoff
2007-04-09 18:14 ` andrey mirtchovski
2007-04-09 21:04 ` ron minnich
2007-04-09 22:01 ` Paweł Lasek
2007-04-09 23:26 ` Kris Maglione
2007-04-10 0:14 ` ron minnich
2007-04-10 0:15 ` erik quanstrom
2007-04-10 0:41 ` Uriel
2007-04-10 7:57 ` Francisco J Ballesteros
2007-04-10 1:08 ` Kris Maglione
2007-04-09 15:50 ` Russ Cox
2007-04-09 16:18 ` Devon H. O'Dell
2007-04-09 16:46 ` matt
2007-04-09 17:51 ` Russ Cox
2007-04-09 17:07 ` Uriel
2007-04-09 17:11 ` Devon H. O'Dell
2007-04-09 17:32 ` Uriel
2007-04-09 18:03 ` ron minnich
2007-04-09 18:07 ` Devon H. O'Dell
2007-04-09 23:03 ` Christopher Nielsen
2007-04-05 21:27 ` W B Hacker
2007-04-05 21:33 ` pedro henrique antunes de oliveira
2007-04-05 21:49 ` Fazlul Shahriar
2007-04-05 21:51 ` pedro henrique antunes de oliveira
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=a0b4fdc70c9531ba9a41193c219915fe@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).