9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fossil/venti falling down?
Date: Thu, 18 Jun 2009 09:21:47 -0700	[thread overview]
Message-ID: <7d3530220906180921h3557c007ga6cb5c9175fe34f9@mail.gmail.com> (raw)
In-Reply-To: <7d3530220906180901l67c7a921v91130a5ea592111e@mail.gmail.com>

On Thu, Jun 18, 2009 at 9:01 AM, John Floren <slawmaster@gmail.com> wrote:
>
> Our Coraid device recently lost two disks from the RAID5
> configuration; while we were able to rebuild from instructions given
> by support, I suspect some small amount of data was corrupted.
>
> Since rebuilding the device a few days ago, every morning I have
> returned to work to find my CPU/auth/file server in a classic "lost my
> file system" state--not locked, but trying to run any command causes
> it to hang. Also, files have been corrupted--here's the top bit of a
> copy of /sys/src/cmd/rio/fsys.c that I was working on:
>  ï¿½
> �   4 "  ï¿½C�/� TEXBASE1ENCODING + DVIPSENCODING TEX-PTMRI8R �H
> } m �����  ï¿½ a a � � �@ �8 � T�
>  ï¿½( �X � � � � � � & 0   !   �� � � � � � � �< �T � f � P � �   � �   � * �@ � . �D �Q4 � < ��t �m> �}E �
> J �X ��Q � T � \ � b � e � k ��m �a} ��� ��� �d ��� �p
>
> Any ideas? I thought maybe fossil was choking somewhere, maybe bad
> info on venti?
>
> Thanks
>
> John

Forgot to add that I've only seen one error on the console during all of this:
/boot/fossil: could not write super block; waiting 10 seconds
/boot/fossil: blistAlloc: called on clean block.

John
--
"I've tried programming Ruby on Rails, following TechCrunch in my RSS
reader, and drinking absinthe. It doesn't work. I'm going back to C,
Hunter S. Thompson, and cheap whiskey." -- Ted Dziuba

  reply	other threads:[~2009-06-18 16:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 16:01 John Floren
2009-06-18 16:21 ` John Floren [this message]
2009-06-18 16:25   ` erik quanstrom
2009-06-18 16:30     ` John Floren
2009-06-18 16:45       ` erik quanstrom
2009-06-18 17:10         ` John Floren
2009-06-24 17:06           ` John Floren
2009-06-21 11:57   ` Richard Miller
2009-06-21 12:12     ` Steve Simon
2009-06-21 14:11     ` erik quanstrom
2009-06-21 19:50       ` Josh Wood
2009-06-24 17:43 ` John Floren
2009-06-24 19:09   ` cinap_lenrek
2009-06-24 23:33     ` John Floren
2009-06-24 23:39       ` erik quanstrom
2009-06-25  0:00         ` Venkatesh Srinivas
2009-06-25  0:42           ` erik quanstrom
2009-06-25 16:13             ` Russ Cox
2009-06-25 16:24               ` erik quanstrom
2009-06-25 16:47                 ` Russ Cox
2009-06-25 16:51                   ` erik quanstrom
2009-06-25  0:59     ` erik quanstrom
2009-06-25 16:13       ` Russ Cox

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=7d3530220906180921h3557c007ga6cb5c9175fe34f9@mail.gmail.com \
    --to=slawmaster@gmail.com \
    --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).