[1223] in SIPB_Linux_Development

home help back first fref pref prev next nref lref last post

Returned mail: Remote protocol error

daemon@ATHENA.MIT.EDU (Mail Delivery Subsystem)
Tue Jan 30 03:24:50 1996

Date: Tue, 30 Jan 96 03:18:52 EST
From: MAILER-DAEMON@MIT.EDU (Mail Delivery Subsystem)
To: owner-linux-help@MIT.EDU

   ----- Transcript of session follows -----
>>> DATA
<<< 550 <rdpalazz@bobp.mit.edu> Host unknown
554 rdpalazz@bobp.mit.edu... Remote protocol error: Bad file number

   ----- Unsent message follows -----
Received: from BOLOGNESE.MIT.EDU by MIT.EDU with SMTP
	id AA04656; Tue, 30 Jan 96 03:18:52 EST
Received: by bolognese.MIT.EDU (5.57/4.7) id AA12937; Tue, 30 Jan 96 03:19:08 -0500
Message-Id: <9601300819.AA12937@bolognese.MIT.EDU>
To: linux-help@MIT.EDU
Subject: <RE>EXT2-fs error & kernel panic
Date: Tue, 30 Jan 1996 03:19:08 EST
From: Renoir / Hoon Kim <hpkim@MIT.EDU>


I had a similar problem a while ago, which told me when I booted linux using
loadlin "ext2-fs error ... kernel panic". (I was running slack 2.1, kernel 
version 1.2.1, as I recall) 

I had to reformat the hard disk and to install the linux from the scratch
(yep, a pain), but I still can't figure out why that happened.  I remember 
that I had about 60% of free space when I typed in "df".  So it's definitely
not the freespace problem.  

My suspicion then was it happened because of my 820 Meg EIDE storage device.  
I still have a very old 486 motherboard without LBA support.  I have an VESA 
Local EIDE controller, but it dosn't have its own BIOS on board.  Anyways, 
even without the on-board EIDE BIOS, Linux kernel seemed to recognize the 
>1024 cylinder HDD.  But, if the way linux handles the hard disk drive is
nothing to do with the BIOS's limitation of 512Mbytes (Excuse me for my 
ignorance), then it's with something else.  

But, most of all, if this kind of *CRASH*ing happens again, I'll have to 
forget about linux for a while till I get a newer computer system.  I 've 
heard this kind of disaster has happened to more than a few people I know 
already. 

[ Some people are even complaining about the "fishy" memory management of linux
  (freemem exhausts as time goes on without any activities), and some are 
  turning to 386FreeBSD. ]

I hope someone could clarify why the ext2 file system tends to crash 
every once in a while.  So I won't have to waste time to reinstall 
linux again. 

Thanks in advance

-Hoon
 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Hoon Kim                          | 
hpkim@mit.edu                     |
http://web.mit.edu/~hpkim/www     |  This area is intentionally left as blank.
450 Memorial Dr. J314             |
Cambridge, MA 02139               |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

home help back first fref pref prev next nref lref last post