A lot of thanks to mulix and Guy that bothered to caution me, and sugested the fixes needed.
Until now the system (an RH7.1) did not showed any adverse features --except that it did not recognize the SCSI disks (they are mentioned on the instalation generated /etc/fstab-- so I guess the system knows about them as the installation was more or less without our intervention- the system must been updating it -like SuSE does on installation). We are going to downgrade it to 2.4.10 which was (I 'm not sure about this) the kernel supplied with RH7.1. (As we use it for Linux benchmark on a large project we'lll fix it asap. , otherwise the bosses won't be pleased about the "new" OS. :) ) BTW, the kernel tried to access the SCSI disks at the time it was 2.4.10, and also without success-but then at least was aware about their existence. Edy mulix wrote: > On Tue, 4 Dec 2001, guy keren wrote: > > > > > On Mon, 3 Dec 2001, Gold Edward wrote: > > > > > We ended up on RH7.1 (2.4.10 & updated afterwards to 2.4.15). > > > > 2.4.15 has a bug that may (and does) cause it to trash filesystems. don't > > use this version - immediastly reset your system, boot with the older > > kernel, and upgrade to some other version (2.4.13, or if 2.4.16 is out - > > then probably 2.4.16. 2.4.14 has a bug that does not allow using > > loopback mounts, unless you add a few lines of fixed code). > > 2.4.16 is out and is stable on all accounts. 2.4.17pre2 is out as well, > if you want to live on the (stable) bleeding edge. > > as for 2.4.15, dont forget to force fsck after you boot from it to a new > kernel. otherwise you could get *silent* data corruption - not a nice > thing by any stretch of the imagination. > > for more information on this bug, peruse this list's archives, the linux > kernel mailing list archives, slashdot or any other linux news source of > your liking. > > p.s. to fix 2.4.14 you have to remove two lines, not add. i know, i > konw, nit picking. can't help it. > -- > mulix > > http://www.pointer.co.il/~mulix/ > http://syscalltrack.sf.net/ > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
