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

2010-05-30 Thread Gregory Pavelcak
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 t

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

2010-05-30 Thread 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

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

2010-05-30 Thread Gregory Pavelcak
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

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

2010-05-30 Thread 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 t

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

2010-05-30 Thread Gregory Pavelcak
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