Date: Sat, 23 Sep 1995 13:34:58 -0700 (PDT) From: Julian Elischer <julian@ref.tfs.com> To: joshk@tanisys.com (Josh Karnes) Cc: hackers@freebsd.org Subject: Re: trouble Message-ID: <199509232034.NAA04257@ref.tfs.com> In-Reply-To: <199509220948.JAA00261@hoover.tanisys.com> from "Josh Karnes" at Sep 22, 95 09:48:58 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > This is going to be along post, but bear with me. I have accumulated a > bunch of problems and I'd like to fill y'all in on some history as well. > > We have a 386DX/8/160/FreeBSD2.0.1 over here that is our mail/web/ftp/slip > (someday... more later) server. We replaced another 386 machine that was > used for the same function, because we were running out of hard disk space > and we kept getting file system errors and we thought the HD was ready to go. > > Well, we just copied everything verbatim from one machine to the other, and > that was months ago. We still get the same nagging error message every day: > > "CLEAN FLAG IS WRONG IN SUPERBLOCK" > "FIX? [yn]" You are not doing this when the system is runnign are you? If so, then this is normal.. you should only do fsck when in singlue user mode, (during boot) before the filesystems are mounted.. and fsck -n is ok to GET AN IDEA of how the health of the fs is, but it will always be slightly wrong, because it's a LIVE MOUNTED fs.. > > We say "y", then reboot, then fsck and get the same error message. > > Recently, we have gotten other file system error messages (forgive me for > not writing them down) something to do with "bitmap", and a bunch of these guys: > > UNREF FILE I=4267 OWNER=root MODE=100600 > SIZE=673 MTIME=Sep 18 17:03 1995 > CLEAR? > > with "I=" a bunch of different values every day. Some other errors too, I > just can't remember them :-) > > So that's problem #1. I need to fix it fast. > Is the system up? an unreffed file is one that a process ahs open but has been deleted.. > ---------- > PROBLEM #2 > ---------- > > SLIP. This has been a serious headache. Let me trace what I have done wrt > SLIP. sorry can't help you on that.. > > 1. Hook up an external Hayes Optima 14.4 modem and enable dialups following > instructions exactly from www.freebsd.org. Set s0=1 and dial in, at any > speed, you get jibberish. For kicks I connect a Microcom 28.8 modem > instead, and dial in and I get a login: prompt like I should. My conclusion > is that there is some speed-matching problem between the modem and the > computer with the Hayes, so I just blow off the Hayes and stick with the > Microcom. > > 2. Start working on SLIP. I configure everything exactly as instructed > from the web pages, and dial in with MacSLIP from (of course) my Mac. After > some tinkering, everything appears to work. Problem is that I can only > communicate directly between the SLIP server and the client, and any packets > bound for anywhere else get nowhere. I can ping the server, but not the Mac > (from the Mac). > > This is how I had this configured: > > 204.96.111.229 ethernet card on the server > 204.96.111.253 serial port on server > 204.96.111.254 serial port on the Mac > > OK, so I know this was wrong. I'm just learnin' all this, ya know. > > 3. Got a good book on TCP/IP. The way I figure, it is a routing problem. > Any packets sent to the client (now configured to the same address as the > SLIP port, 204.96.111.253 on both ends of the serial connection) from some > other host are not being forwarded from the ethernet card to the SLIP > interface. After much deliberation, I concluded (for some reason that > sounded good then but I can't remember now) that I needed to add the "-s" > flag to routed. The pseudo-proxy-arp, btw, far as I can tell, has been > configured properly all along. So I add "-s", as well as changing the > addresses so they are the same on both ende of the SLIP line, and just when > I think it is going to work... > > 4. Dial in, get jibberish !@%$!@#$!@# Just like the jibberish I got when I > dialed in with the Hayes modem. Oh, did I mention that there was a power > outage and the modem's memory (semi-volatile) got flushed? Can't even log > in with a terminal (non-slip) connection anymore. It seems like a baud rate > problem, or some other modem settings problem, but I think everything is set > right! What gives??? > _____________________________________________________________________________ > Josh Karnes joshk@tanisys.com > Senior Communications Specialist http://www.tanisys.com/~joshk/home.htm > Tanisys Technology http://www.tanisys.com > Austin, Texas '72 240Z | IZCC #308 > _____________________________________________________________________________ > *** opinions expressed herein are MINE, ALL MINE!! *** > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509232034.NAA04257>