Re: kern/34461 (multiple problems; lfs-related)

[Bert Kiers <kiersb%xs4all.net@localhost>]

The following reply was made to PR kern/34461; it has been noted by GNATS.

From: Bert Kiers <kiersb%xs4all.net@localhost>
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%NetBSD.org@localhost, 
netbsd-bugs%NetBSD.org@localhost,
        gnats-admin%NetBSD.org@localhost, dholland%NetBSD.org@localhost
Cc: 
Subject: Re: kern/34461 (multiple problems; lfs-related)
Date: Sun, 13 Jul 2014 14:55:39 +0200

 On 7/12/14 7:20 PM, dholland%NetBSD.org@localhost wrote:
 > Synopsis: multiple problems; lfs-related
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: dholland%NetBSD.org@localhost
 > State-Changed-When: Sat, 12 Jul 2014 17:20:30 +0000
 > State-Changed-Why:
 > If there's anyone still on the other end of this... is there any reason to
 > believe this wasn't a driver or hardware issue? The fact that the problem
 > starts with a driver-level error makes me think it probably isn't LFS.
 > 
 > Reformatting with FFS and no longer seeing the issue doesn't really prove
 > anything as FFS has much different I/O patterns, and in particular when
 > rsyncing LFS will be ramming a lot more data down the disk system's throat.
 > (Or at least, a lot more at once.) If there was a load- or timing-dependent
 > problem at the disk level it's quite possible that FFS wouldn't trigger it,
 > especially if you weren't using softupdates.
 
 System is scrapped. If somebody is really interested I could retry with
 newer computer, NetBSD-current and same box with disks.
 
 
 -- 
 Bert Kiers
 XS4ALL UNIX systeembeheerder, suspected terrorist
 1984 was not meant as a manual