Subject: Re: port-sparc64/37485: corrupted ffs
To: None <,,>
From: Salvador Fandino <>
List: netbsd-bugs
Date: 12/08/2007 21:30:02
The following reply was made to PR port-sparc64/37485; it has been noted by GNATS.

From: Salvador Fandino <>
Subject: Re: port-sparc64/37485: corrupted ffs
Date: Sat, 8 Dec 2007 13:25:26 -0800 (PST)

 [Reposted. It seems that gnats did not like 
 the message as encoded by Yahoo to handle the non-ascii letter on my 
 john heasley wrote:
 > you should check that your / and swap partitions do not overlap
 "sysinst" takes care of that, doesn't it?
 I only have to specify the partition
 sizes and it arranges them on the disk. BTW, I have partitioned the
  disk so
 that all the space is used, it says "0 blocks free" (or something
 Anyway, one of the times, (I am writing from memory)
  became corrupted, and looking at the file, I saw that the ELF header was
  corrupted at the byte level, instead of the tree "ELF" bytes it had
  something like "OLF". I think that this could only be caused by defective
  hardware (HD or controler) or a bug on the DMA/IO layer.
 Broken RAM could be also the cause but besides the FS corruption, the
  machines were completely stable what makes it unlikely and as I tried
  NetBSD on two (identical) machines with the same result, and FreeBSD
  worked there, I would discard any hardware problem as the cause of the
 Next Monday I would try to get the dmesg output and make some more test
  using "dd"
 - Salva
 Be a better friend, newshound, and 
 know-it-all with Yahoo! Mobile.  Try it now.;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ