From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] Using cwfs
Date: Tue, 25 Aug 2009 00:13:37 +0200 [thread overview]
Message-ID: <194962e34f2d24f5d99023112eabba39@gmx.de> (raw)
In-Reply-To: <fe41879c0908241338o309657d0t7a9ab0702891055a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
check if you have the latest version of /sys/src/cmd/cwfs/wren.c
from sources.
the old wrenread()/wrenwrite() used non atomic seek/read/write
sequence that leaves a window for another process moving the file offset
arround under you. this caused wired checktag errors when i tried
to copy my main fileserver to another freshly created cwfs.
--
cinap
[-- Attachment #2: Type: message/rfc822, Size: 3997 bytes --]
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Using cwfs
Date: Mon, 24 Aug 2009 16:38:51 -0400
Message-ID: <fe41879c0908241338o309657d0t7a9ab0702891055a@mail.gmail.com>
I believe there may be an inconsistency somewhere
in the dump records themselves. When I tried to
copy back the file from the dump, into the active
fs, after a while of copying, cwfs panicked with:
main grow ...
tag = 5/23; expected 757/7 -- not flushed
panic: cwio: checktag c bucket
halted ...
So I ran a `check' after starting up cwfs again, but
nbad = 0
nqbad = 0
although
nmiss = 224455
and still I don't know whether the nmiss is something
that ought to be fixed, or how.
Anyways, the check doesn't seem to reveal any
tag inconsistencies - any suggestions for further tests
in revealing what might be the issue? Or possible
fixes?
Thanks,
ak
next prev parent reply other threads:[~2009-08-24 22:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 7:37 Akshat Kumar
2009-08-23 12:54 ` erik quanstrom
2009-08-23 13:07 ` Anthony Sorace
2009-08-23 20:05 ` Akshat Kumar
2009-08-24 1:45 ` Akshat Kumar
2009-08-24 2:11 ` Akshat Kumar
2009-08-24 3:27 ` erik quanstrom
2009-08-24 3:53 ` Akshat Kumar
2009-08-24 11:10 ` Mathieu L.
2009-08-25 20:55 ` erik quanstrom
2009-08-24 20:38 ` Akshat Kumar
2009-08-24 22:13 ` cinap_lenrek [this message]
2009-08-25 20:56 ` erik quanstrom
2009-08-27 1:24 ` Akshat Kumar
2009-08-27 3:29 ` erik quanstrom
2009-08-27 14:09 ` Francisco J Ballesteros
2009-08-27 14:16 ` erik quanstrom
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=194962e34f2d24f5d99023112eabba39@gmx.de \
--to=cinap_lenrek@gmx.de \
--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).