From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] kenfs config? (was: OT: scsi sense error code hardware
Date: Wed, 18 Oct 2006 01:55:08 +0200 [thread overview]
Message-ID: <200610172355.k9HNt9t02813@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Tue, 17 Oct 2006 17:35:19 -0400." <8e5ff4336634d17b0c3f6cfe8e7eb612@plan9.bell-labs.com>
> There's still the question of how to initialise the second device in
> the mirror-to-be. I would have copyworm-ed f(w5w1) to f(w2). I'm
> nervous that copying from cw0f(w5w1) may not yield exactly the same
> bytes as copying from f(w5w1).
Ok, thanks! I've tried looking at the code but (at this time of day)
initially only got more confused - /sys/src/fs/port/config.c:^wormof
seems not get the worm part of a cw, which is what I would expect it
to do (instead, it seems to take are of a cw within an fworm?).
I then realized that the copyworm code I run today was older:
/n/sourcesdump/2003/0314/plan9/sys/src/fs/port/config.c
it did copy the f(w5w1) part of cw0f(w5w1) (the written blocks).
copying worm from f(w5w1) to fw2, starting in 8 seconds
limit 1505835
copying worm
fworm: read 0
0 not written
fworm: read 1
1 not written
block 20000 Tue Oct 17 15:57:26 2006
[...]
copied 1505835 blocks from f(w5w1) to fw2
Even earlier today I had tried the same with the slightly newer kernel
(code from march 14 2003) which I had patched to allow recover to work,
and then it not only did not give exactly the same bytes, but it failed:
copying worm from cw0f(w5w1) (worm cw0f(w5w1)) to fw2, starting in 8 seconds
devsize(cw0f(w5w1)) = 1505936
fworm: read 0
i/o error reading cw0f(w5w1) block 0
panic: no blocks to copy on cw0f(w5w1)
I did not compare in detail, but the code seems to be essentially
the same as in the current version on sources.
my first superblock seems to be block 2 - that explains fworm: read 0?
related to the 'fworm of mirror' vs. 'mirror of fworms':
I guess that copyworm would not be able to deal with the case of
'cached worm where worm is mirror of fake worms' (or would it?)
Axel.
(turns out I have to redo the copy anyway because confused by
the big numbers of half-k and 4k blocks I chose a too small w2 disk
that won't allow much growth - but is was big enough to hold the
written part of f(w5w1) so I guess at least I have a backup)
next prev parent reply other threads:[~2006-10-17 23:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 13:10 [9fans] OT: scsi sense error code hardware error 40 83? Axel Belinfante
2006-10-03 18:17 ` geoff
2006-10-03 20:13 ` [9fans] kenfs config? (was: OT: scsi sense error code hardware error 40 83?) Axel Belinfante
2006-10-03 21:19 ` [9fans] kenfs config? (was: OT: scsi sense error code hardware geoff
2006-10-17 15:55 ` Axel Belinfante
2006-10-17 20:18 ` geoff
2006-10-17 21:05 ` Axel Belinfante
2006-10-17 21:35 ` geoff
2006-10-17 23:55 ` Axel Belinfante [this message]
2006-10-03 20:20 ` [9fans] gs Charles Forsyth
2006-10-03 20:39 ` geoff
2006-10-03 20:41 ` Francisco J Ballesteros
2006-10-03 20:48 ` Jack Johnson
2006-10-03 21:37 ` LiteStar numnums
2006-10-03 22:07 ` Andy Newman
2006-10-04 2:18 ` jmk
2006-10-06 0:00 ` Bruce Ellis
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=200610172355.k9HNt9t02813@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).