I have a Linux box that I upgraded from 7.2 to 8.0. For some reason and on occasion, when you open up an application, the system freezes up to
the point that you have to do a hard reboot. However, when you do the reboot, the OS wants you to do a FSCK on the system which is usually no
problem, but in this case, it usually takes over two hours or more to do the check! Should I try to reduce the check time and the amount of files
being checked, or should I just try and do a fresh install of this system? Its a specialty machine with unique software so I?m trying to resolve as much as I can before I have to consider the extremes. Originally the complete install was done when the upgrade option “didn’t work”, and all but two data drives wereconverted from 7.2 to 8.0; A home directory and another data drive. Afterwards, this is when I started having problems. Initially, when the system comes back up and request an fsck, it will start with the following messages:
“unattached inode ########, connect to /lost+found?, yes
“inode ###### ref count is 2, should be 1, Fix?, yes.
These unattached inode numbers (#######) can go from 1 to over 300000 before the
darn thing finally is finished! Is there any way around this before
I have to take the drastic measure of going to RH9?
-Also-
Is it possible to go back to an older version of linux, say from 8.0 back to 7.2?
PS,
the machine is a Dell Demision tower.