9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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: Tue, 17 Oct 2006 17:55:02 +0200	[thread overview]
Message-ID: <200610171555.k9HFt3728837@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Tue, 03 Oct 2006 17:19:38 -0400." <9dc713f8017f9ffce2797522dcf318df@plan9.bell-labs.com>

> Right, you could just configure the cache as mirrored disks and
> recover main.  The mirror device does not copy new devices when they
> are added to a mirror; you'd need to copydev first (or boot as a cpu
> server and use dd) to copy the original disk to its mirror disks).

finally I had time to look at my fs.
seems I'm lucky: the fake worm is ok.

I've replaced the cache disk and recovered; I encountered
'panic: fworm: rbounds 13219302' (my fs kernel is a bit old (2003))
but the fix mentioned here a while ago (fix conf.firstsb) worked.

since I wanted a backup (and if possible: mirror) 'right now' even
though my /sys/src/fs is out of date and does not yet have copydev,
and I don't want to pull a lot of changes from sources right now,
I tried copyworm
from:  filsys main cw0f(w5w1)
to:    filsys output f(w2)

this seems to have worked, but I have not yet accessed the result
(just switched off the machine while it looped after copyworm).

now my real question is:
would it be ok to use the copy f(w2) as mirror,
as in    filsys main cw0{f(w5w1)f(w2)}    ?

Axel.


  reply	other threads:[~2006-10-17 15: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 [this message]
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
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=200610171555.k9HFt3728837@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).