From: "Oleg Finkelshteyn" <olegfink@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] venti icachewriteproc going past isect
Date: Thu, 8 Jan 2009 01:34:25 +0300 [thread overview]
Message-ID: <7dfd70b00901071434g2aeefb6frdd00b0e88d151e15@mail.gmail.com> (raw)
hi,
i've had this behavior some time ago and haven't solved that, and now
Akshat Kumar is experiencing exactly the same, but as the venti at
faul is running on his mail server, he's unable to post here.
as soon as venti starts, an icachewriteproc can be observed which
produces high load, making the whole system unresponsive:
bootes 13 0:00 0:27 42392K Pwrite venti
[icachewriteproc:/dev/sdC0/isect]
from /proc/13/fd it can be seen that its offset into /dev/sdC0/isect
keeps increasing, even past the partition size:
% ls -l /dev/sdC0/isect
--rw-r----- S 0 bootes bootes 3175279616 Aug 22 23:38 /dev/sdC0/isect
% cat /proc/13/fd
8 rw S 0 (0000000004300066 1 00) 0 3223880192 /dev/sdC0/isect
this always reproduces after a restart.
killing icachewriteproc renders fossil unresponsive, essentially
making system unusable.
fshalt -r hangs at 'syncing.../srv/fscons...', so the machine can't be
rebooted cleanly.
any hints?
thanks,
oleg
reply other threads:[~2009-01-07 22:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7dfd70b00901071434g2aeefb6frdd00b0e88d151e15@mail.gmail.com \
--to=olegfink@gmail.com \
--cc=9fans@9fans.net \
/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).