[no subject]

3.FS Corruption With Later 2.2.x?

    Subject: Massive e2fs corruption with 2.2.9/10?

    This was a long thread, in which several people reported filesystem
corruption on the later 2.2.x kernels. None of the
    major developers were able to reproduce the problems, however. At
one point, Stephen C. Tweedie said, "Well, after
    an hour or so of hammering a large 2.2.10 (build on egcs-1.1.2) SMP
box with all manner of lmdd big file
    copies/compares, 100 process and 150 process dbench stressers,
parallel kernel builds and concurrent NFS loading,
    absolutely nothing has gone wrong for me." 

    Then one by one, most or all of the reports were shown to be
probably hardware related (bad ram, overclocked CPUs,
    etc), although it did seem like one or two might be actual kernel
problems. 

Wye Enterprises wrote:
> 
> > ---------- Forwarded message ----------
> > Date: Thu, 10 Jun 1999 16:01:17 +0530
> > From: prasad <prasadb@xxxxxxxxxx>
> > To: ilughyd List <ilughyd@xxxxxxxxxxx>
> > Subject: Warning - RH 6.0 smbfs corruption with NT
> >
> > ILUG-HYD Mailing List - http://linuxindia.virtualave.net
> >
> > Saw this on lwn -
> >
> > Do not use the stock Red Hat 6.0 kernels with smbfs
> > if you are mounting shares from Windows NT,98, or 2000
> > servers. A message from Michael Warfield explains why:
> > the stock kernel has been built with a compile option
> > that causes smbfs to only work with Windows 95 servers.
> > All others will see corruption in the file timestamps.
> > If you are running Red Hat 6.0 on a network with Windows
> > servers,you will probably need to build and install
> > your own kernel.

- --------------------------------------------------------------------
For more information on Linux in India visit http://www.linux-india.org/

------------------------------

End of Linux India Digest V1 #85
********************************

--------------------------------------------------------------------
To unsubscribe send an email to majordomo@xxxxxxxxx with the word
'unsubscribe linux-india-digest' (without the quotes) in the body
of the email.