Re: [MiNT] Serious problem with Minixfs

[tos4ever@online.be (Martin "Nightowl" Byttebier)]

on Mon 18-10-1999 19:34 johnnie ligotage wrote:

>On Mon, 18 Oct 1999, Martin Nightowl Byttebier wrote:
>> Today I ran into a serious problem on my Hades.
>> For some reason Cab 2.7e crashed when I try to launch it (with MiNT-ovl) 
>> and took down the whole system.
>
>Yes! A very nasty problem. I have 2.5 here, and it does the same sort of
>thing. Were you running Apache to look at some web docs on your local box?

No, I wasn't. I was online and wanted to launch Cab 2.70. When it did the 
initialising it just frooze up and so did the whole system too.
The apache server was up however (part of the MiNT'98 CD-ROM).
I must say that just before I try to launch Cab I killed aftp because I 
couldn't get a connection to the ftp-server I was trying to visite.
 
>I've been developing some cgi scripts using an Apache port compiled with
>the proxy module that I put on my home page, but have given up using cab
>to check them, as it eventually takes out my root partition and takes me
>half an hour to get it back. I'm using Franks latest ext2fs.

I'm using on both my MiNT partitions minixfs. Drive 'l' which crashed 
yesterday holds the complete MiNT '98 CD-ROM setup. I adapted that setup 
to suite RPM.

>
>I would guess that it is the ovl. Maybe when it tries to resolve a
>hostname? 

As said above Cab wasn't up and running yet when the whole system frooze 
up.

>I don't know, but CAB here is set up to keep well away from
>from my *nix partitions, but it will trash the root, eventually. CAB's
>cache is on a TOSFS, so I don't think that is affecting anything. When I
>was running apache as a caching proxy server - great for speed - it was
>always a cache file that e2fsck would complain about. I have since
>disabled that, but still it would trash.

Cab is running on a newfatfs (with VFAT) partition. The cache is set to 
another newfatfs/VFAT. I'm using the ssl.ovl

>> first minix the system halted for some time, then I got this horrible 
>> message: minix-FS (L): root inode is not a directory?
>> (Drive 'L' is were all the MiNT stuff is located)
>
>If you were using ext2fs, you would get a similar message saying try
>running 'e2fsck -b 8193 l' or similar. I don't think you can do this with
>minix-fs.

Not sure but I thought I got a message saying that the system was unable 
to run fsck on drive l.

>> I wonder if there was a better way to bring back alive that drive?
>
>Try the ext2fs: and run Franks 'fscheck.sh' from your mint.cnf. That would
>allow you greater security, especially if you copy a few other useful
>utils to c:\mint\bin (or wherever) like reboot, debugfs, cp, ls, rm, grep,
>mv, sh (this is purely a personal selection) and rename them to *.ttp. You
>should then limit the path at boot-time to just \boot\mint\bin or
>c:\mint\bin and change all the commands in fscheck.sh to *.ttp. I even get
>fscheck.ttp to grep \boot\mint\etc\fstab for my drives (and link
>/etc/fstab to it).

Maybe I should give ext2fs a new try. I've tried it once on my TT030 but 
everytime I booted up the TT030 I got a whole bunch of warnings. I believe 
it took me some 2 minutes to answer these warnings so I dumped it.
>
>> For your information. I'm using freeMiNT 1.15.4b and minixfs-0.72
>
>I think we'll find it is independant of the os version etc, unless it has
>only started to happen since 1.15.1 or so.

That's what I fear more or the less. Until yesterday I never got any 
problem with Cab. I have used every new beta since 1.14.

TTFN
Martin
-- 
O-Tagger ß1.24: It's a bird, It's a plane, <SPLAT>... It's a bird.
              ***** Greetings from Okami Newsreader *****
              **  On the seventh day He created Atari  **
                ********** tos4ever@online.be ***********
                         ** ICQ 37138054 **
              But He uses a freeMiNT powered Hades 060 now
        UTSI: http:/user.online.be/~ols04484/atari/prg-ind.htm
           Atari FTP-site: ftp://chapelie.rma.ac.be/atari/