9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] more fossil woes
Date: Sat,  1 Nov 2003 00:56:10 -0700	[thread overview]
Message-ID: <Pine.LNX.4.44.0311010051180.9312-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <5a828837c6470dfc75b135b56c038ebe@plan9.bell-labs.com>

On Fri, 31 Oct 2003 jmk@plan9.bell-labs.com wrote:

> I'd say you had something more fundamental wrong, or else you're not telling
> the whole story. If you do the 2nd flfmt as described below you should
> get a message like
> 	fs header block already exists; are you sure? [y/n]:
> unless you have the '-y' option.
>

there is no message, fossil dies absolutely immediately after I type the
command (and before I had done the 'cat /dev/zero > /dev/sdC0/fossil' there
was no corruption on the disk whatsoever, so after each crash I rebooted
safely from either devfs or the first disk on the box).

the only thing suspect for me is the earlier crash with nblock > 1, which I
have no way of debugging anymore -- there was no log trace of that crash,
except what I had logged on a different machine from the serial console.

if you think i'm omitting something important -- tell me what it could be, so i
can try and help...

andrey



  reply	other threads:[~2003-11-01  7:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-01  0:24 andrey mirtchovski
2003-11-01  4:18 ` jmk
2003-11-01  7:56   ` andrey mirtchovski [this message]
2003-11-01  5:35 ` Russ Cox
2003-11-01  7:50   ` andrey mirtchovski
2003-11-11  4:59 ` Russ Cox
2003-11-11  4:35   ` mirtchov
2003-11-11  6:08     ` Russ Cox
2003-11-11  6:08     ` andrey mirtchovski
2003-11-11  9:16     ` Richard Miller
2003-11-11  9:59       ` Lucio De Re
2003-11-11 10:36         ` David Lukes

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=Pine.LNX.4.44.0311010051180.9312-100000@fbsd.cpsc.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).