From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] missing venti arenas
Date: Mon, 23 Feb 2004 11:30:22 +0100 [thread overview]
Message-ID: <8e3db087739aa7ab350112348e9493f6@plan9.escet.urjc.es> (raw)
In-Reply-To: <be1d29ebb742f4f72821ee3dbda24bee@mteege.de>
[-- Attachment #1: Type: text/plain, Size: 159 bytes --]
Don't you see `arenas0' when you do
lc /dev/sdC1
if that's the case there's a missing
disk/prep -p /dev/sdC1/data >/dev/sdC1/ctl
in your start script.
[-- Attachment #2: Type: message/rfc822, Size: 2882 bytes --]
From: Matthias Teege <matthias@mteege.de>
To: 9fans@cse.psu.edu
Subject: [9fans] missing venti arenas
Date: Mon, 23 Feb 2004 10:18:22 0000
Message-ID: <be1d29ebb742f4f72821ee3dbda24bee@mteege.de>
Moin,
last week I described a problem with venti setup. I prepared the
disk and format venti areans and index but after reboot I missing
the areanas and index. It looks like that:
term% disk/prep /dev/sdC1/data
empty 0 2 (2 sectors, 1.00 KB)
arenas0 2 3670018 (3670016 sectors, 1.75 GB)
arenas1 3670018 7340034 (3670016 sectors, 1.75 GB)
isect0 7340034 7864322 (524288 sectors, 256.00 MB)
isect1 7864322 8388608 (524286 sectors, 255.99 MB)
>>> q
term% ls /dev/sdC1
/dev/sdC1/ctl
/dev/sdC1/data
/dev/sdC1/plan9
/dev/sdC1/raw
term% ls /dev/sdC1/data
/dev/sdC1/data
term%
term% venti/fmtarenas arenas0 /dev/sdC1/arenas0
fatal venti/fmtarenas error: cant open partition /dev/sdC1/arenas0: cant open partition=/dev/sdC1/arenas0: fd out of range or not open
term%
Thanks for any hint
Matthias
next prev parent reply other threads:[~2004-02-23 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 10:18 Matthias Teege
2004-02-23 10:30 ` Fco.J.Ballesteros [this message]
2004-02-23 13:46 ` Matthias Teege
2004-02-23 14:47 ` Fco.J.Ballesteros
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=8e3db087739aa7ab350112348e9493f6@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).