| To: | Seth Mos <knuffie@xxxxxxxxx> |
|---|---|
| Subject: | Re: severe fs corruption |
| From: | Utz Lehmann <leh@xxxxxxxxxxxxxx> |
| Date: | Tue, 12 Jun 2001 20:18:44 +0200 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <4.3.2.7.2.20010612193034.02fc2210@xxxxxxxxxxxxx>; from knuffie@xxxxxxxxx on Tue, Jun 12, 2001 at 07:32:19PM +0200 |
| References: | <4.3.2.7.2.20010612193034.02fc2210@xxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
Hi We also have a lot of trouble with bad DIMMs here. If something got strange, we do a RAM check first. We are using memtest86 (http://reality.sgi.com/cbrady_denver/memtest86/) which is really nice. Run it for a few passes. If there no errors, the trouble is caused by something else. If you got RAM errors, dont even think about another cause (until the RAM is fixed). utz Seth Mos [knuffie@xxxxxxxxx] wrote: > Hi, > > I just got feedback about the report with subject "Re: severe fs > corruption" which was led back to a faulty memory Dimm. > > The report can be scuffed. > > Cheers > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS and knfsd, Kirk Thoning |
|---|---|
| Next by Date: | Re: severe fs corruption, Seth Mos |
| Previous by Thread: | Re: severe fs corruption, Seth Mos |
| Next by Thread: | Re: severe fs corruption, Seth Mos |
| Indexes: | [Date] [Thread] [Top] [All Lists] |