the subject heading was sort of deliberatly inflammatory - I'm at my wits
end. I've had linux 1.0.9's (slackware) FS corrupt 7 times in 7
installations, either directly after the install or as long as 4 hours &
1 or 2 legal shutdowns. before I go further:
386dx40, 4 meg ram, 2 40 meg ide hard drives (a mitsumi and a fuji), #2
being linux native (32 meg) and linux swap (the remaining 8). there's a modem
on com2, MS mouse on com1, and an Oak 077 svga card. I've done nothing fancy
to the guts of my machine, in fact my version of bios really won't let me
change much (ami ~1991) I suppose I should know, but I can't exactly say
what the chipset is, though I think it's opti.
To continue: after simple use, nothing more than running minicom or doing
some other very trivial program running (I don't yet know enough about
unix to go near the internals) I notice that files start acquiring strange
attributes. directories turn into files (my /sbin was suddenly a file,
but had the contents of /etc/rc.d/rc.S as it's text) another directory
turned from drwxrw-rw into ?---------. some files are reported as being
gigantic, as much as 300 gig. Very soon, the device simply fails to boot,
or will only come on in read only mode.
I saw one post that suggested it was possible for the swap partition to
overlap the native partition, but I checked w/ fdisk and mine apparently
does not (linux native going from 1 to 774, linux swap from 775 to 975)
once among my 7 installations attempts, linux didn't live complete long
enough for me to do the first shutdown (it reported it couldn't run
/bin/su, which wasn't surprising. /bin/su was 20megs, and no longer
executable in permissions.
I've been choosing the slow format on installing and get no errors (ext2)
and yet after the first shutdown, fsck starts reporting inode problems
oh, a final pertinent fact, I haven't even installed anything beyond the
a disks in most of these cases.