From: erik quanstrom <quanstro@quanstro.net>
To: pavelcak@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] Ken's FS: WORM Superblock read failed
Date: Sun, 30 May 2010 11:56:56 -0400 [thread overview]
Message-ID: <9bf92ba26e3764c414036a3537da24e5@kw.quanstro.net> (raw)
In-Reply-To: <AANLkTim_QTuJrjz6VcMuukfXtq3iijPJK0JgrDkHi6qj@mail.gmail.com>
> Yesterday, I configured a file server with two IDE drives as ch0fh2. The
> setup seemed to go OK, but one of the last things on the screen before it
> brought the server up is in the subject line: WORM Superblock read failed.
> It also said something about block 2 (I know the numeral `2' was in there).
>
> When I booted this morning and let it go through the whole process, I got:
> tag = Tnone/0: expected Tbuck/2697 -- flushed (2697)
> panic: cwinit: ??? tag c bucket
if you booted from one of these drives, you may have stepped on
the partition table and/or configuration.
have you tried "recover main" at the configuration prompt?
i'd recommend making the cache relatively small. p10.10 might be
a good plan.
>
> Motherboard is ECS L4S5MG with SiS 650/961 chipset
> Hard Drives are both Western Digital WD800JB (80G ATA drives)
> The kernel is 9fsfs64 from /sources/extra/kensfs.tgz. I don't know if Erik's
> fs has mods that are relevant. I haven't tried his contrib version yet.
if you do use it, you can partition the drives with prep and/or
fdisk and use partition names. percentage is pretty sloppy when
you get to an 80gb drive. i found that absolute sector numbers
are error prone for humans to type and sharing an aoe target
makes sense. here's my main configuration
filsys main cpe2.0"kcache"e2.1
- erik
next prev parent reply other threads:[~2010-05-30 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 15:25 Gregory Pavelcak
2010-05-30 15:56 ` erik quanstrom [this message]
2010-05-30 16:48 ` Gregory Pavelcak
2010-05-30 16:53 ` erik quanstrom
2010-05-30 17:14 ` Gregory Pavelcak
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=9bf92ba26e3764c414036a3537da24e5@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=pavelcak@gmail.com \
/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).