From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: [9fans] kfs locks
Date: Sun, 7 Mar 2004 21:55:37 +0400 [thread overview]
Message-ID: <200403071755.i27HtbcR080605@adat.davidashen.net> (raw)
Hi,
cmd_sync sets
rlock(&mainlock);
...
syncall();
...
runlock(&mainlock);
...
syncproc, the background process forked by kfs, runs
syncblock()
without setting rlock(&mainlock)
Can it the cause that I am getting wrenwrite errors after
'check f' on startup, if cmd_sync is not called after cmd_check
and before forking 'sync' and 'serve'?
I am still struggling to understand the problem. I've changed
the disk to be sure and still can reproduce the error if cmd_sync
is not called after the list of free blocks is rebuilt after blackdown.
David Tolpin
next reply other threads:[~2004-03-07 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 17:55 David Tolpin [this message]
2004-03-07 19:56 ` Charles Forsyth
2004-03-07 20:03 ` David Tolpin
2004-03-07 20:12 ` Charles Forsyth
2004-03-07 20:20 ` David Tolpin
2004-03-08 3:27 ` jmk
2004-03-08 5:26 ` David Tolpin
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=200403071755.i27HtbcR080605@adat.davidashen.net \
--to=dvd@davidashen.net \
--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).