[9fans] Ken's FS: WORM Superblock read failed

[9fans] Ken's FS: WORM Superblock read failed

[Gregory Pavelcak]

[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]

Hi,

I've been messing around with setting up a Ken's file server with old
hardware that's accumulated over the years.

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

(Embarrassing. The "???" indicates where I can't read my own handwriting.)

Any insight would be appreciated.

Here's some more setup info:

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.

Thanks.

Happy long weekend to those of you who have one.

Greg

[-- Attachment #2: Type: text/html, Size: 1183 bytes --]

Re: [9fans] Ken's FS: WORM Superblock read failed

[erik quanstrom]

> 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

Re: [9fans] Ken's FS: WORM Superblock read failed

[Gregory Pavelcak]

[-- Attachment #1: Type: text/plain, Size: 2852 bytes --]

I didn't try recover, but since the config I really want is a partitioned
one like you suggest, and the errors I reported didn't make anyone
immediately think "dying hard drive"; I think I'll try getting your (Erik's)
fs from contrib.

I assume I can do something like this:

Put the two hard drives destined to be on the file server on my existing
fossil-only machine (I have a hard drive with that somewhere from the last
few days of experimentation).

Diskpart and diskprep those drives with, for example, 9fat, cache, and worm
on the drive destined to be h0 on the server and 9fat, other and worm on h2.
Using some appropriate sizes (approx 10% of disk size going to cache and
other with h0."worm" and h2."worm" the same size for mirroring).

Put 9load, plan9.ini, a kernel from fs on h0.9fat (Something missing? I
guess I just want to emulate what pc/bootfloppy would do for me, but I want
to copy those things to h0.9fat.)

Move the disks to the file server, boot, watch everything come up just fine,
and config something like:
  filsys main cph0."cache"f{ph0."worm"h2."worm"}
  filsys dump o
  filsys other ph2."other"

I'd appreciate it if someone would let me know if I'm way off base here.
Otherwise, I'll probably give this a shot this afternoon or tomorrow.

Thanks.

Greg

On Sun, May 30, 2010 at 11:56 AM, erik quanstrom <quanstro@quanstro.net>wrote:

> > 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
>

[-- Attachment #2: Type: text/html, Size: 3598 bytes --]

Re: [9fans] Ken's FS: WORM Superblock read failed

[erik quanstrom]

>   filsys main cph0."cache"f{ph0."worm"h2."worm"}
>   filsys dump o
>   filsys other ph2."other"

should be

	filsys main cph0"cache"f{ph0"worm"h1"worm"}
	filsys dump o
	filsys other ph1"other"

also recommend against using the "f" fake worm device.
it makes changing the size of the device (say by 1 sector)
excessively difficult, and i'm unclear on the actual upside;
if the fake worm device saves you, things are already
pear shaped.

- erik

Re: [9fans] Ken's FS: WORM Superblock read failed

[Gregory Pavelcak]

[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]

Thanks Erik.

Yeah, the "f" device is just a consistent brain tic for me. Once upon a time
I thought for some reason that "f" always went with "c" unless you were
using a real jukebox, and now I can't seem to get rid of that
misapprehension when I write my configs.

I used "h2" because I intended to have the drives on separate controllers.
Are you saying it should be "h1"  even if there is no primary slave, or are
you recommending that I put the drives on a single controller?

Getting optimistic about trying this.

It seems to me from my lurking around the groups that Erik is almost
single-handedly keeping Ken's FS alive. I would just like to voice my
appreciation for that.

Greg




On Sun, May 30, 2010 at 12:53 PM, erik quanstrom <quanstro@quanstro.net>wrote:

> >   filsys main cph0."cache"f{ph0."worm"h2."worm"}
> >   filsys dump o
> >   filsys other ph2."other"
>
> should be
>
>        filsys main cph0"cache"f{ph0"worm"h1"worm"}
>        filsys dump o
>        filsys other ph1"other"
>
> also recommend against using the "f" fake worm device.
> it makes changing the size of the device (say by 1 sector)
> excessively difficult, and i'm unclear on the actual upside;
> if the fake worm device saves you, things are already
> pear shaped.
>
> - erik
>

[-- Attachment #2: Type: text/html, Size: 1856 bytes --]