From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] cwfs
Date: Fri, 22 Feb 2013 20:33:26 +0900 [thread overview]
Message-ID: <AC7056FC-F590-4063-A77B-69C1186EBB5F@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <6c5658ae83ba1e8e1c89d2e55cc57ab6@brasstown.quanstro.net>
Thanks, erik and cinap,
I have believed that tag/path of first block in fscache is to be created by config mode.
but not.
I retried complete copy (16KB copy) of the first block of fscache.
as erik pointed me.
recover main
end
is enough.
thanks again
Kenji Arisawa
On 2013/02/22, at 19:40, erik quanstrom <quanstro@quanstro.net> wrote:
>> the response were:
>> check tag PC=12336 w"/dev/sdC0/fscache"(0) tag/path=<badtag> /15.....36: expected <nil>
>> and then returned back to the selection prompt.
>>
>> why tag/path in fscache is the problem in recovering?
>> they must be cleaned based on fsworm.
>
> on the real file server, the command is
>
> recover main
>
> note the fs name. and one would expect a stream of
> "dump %lld is good; %lld next\n" messages.
>
> peeking at the source, i would expect similar from
> cwfs.
>
> - erik
>
next prev parent reply other threads:[~2013-02-22 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 8:11 arisawa
2013-02-22 8:55 ` cinap_lenrek
2013-02-22 10:15 ` arisawa
2013-02-22 10:25 ` arisawa
2013-02-22 10:40 ` erik quanstrom
2013-02-22 11:33 ` arisawa [this message]
2013-02-22 11:43 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2009-05-08 16:27 cinap_lenrek
2009-05-08 16:39 ` erik quanstrom
2009-05-08 17:56 ` cinap_lenrek
2009-05-08 19:10 ` erik quanstrom
2009-05-08 19:39 ` cinap_lenrek
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=AC7056FC-F590-4063-A77B-69C1186EBB5F@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--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).