NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/50707: rm: fts_read: No such file or directory



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

From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand%systella.fr@localhost>
To: Christos Zoulas <christos%zoulas.com@localhost>, gnats-bugs%NetBSD.org@localhost,
        kern-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost,
        netbsd-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Tue, 26 Jan 2016 14:50:58 +0100

 Christos Zoulas a écrit :
 > On Jan 26,  8:37am, joel.bertrand%systella.fr@localhost (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
 > -- Subject: Re: kern/50707: rm: fts_read: No such file or directory
 >
 > | Christos Zoulas a écrit :
 > | > On Jan 25, 11:35pm, joel.bertrand%systella.fr@localhost (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
 > | > -- Subject: Re: kern/50707: rm: fts_read: No such file or directory
 > | >
 > | > | 	I would prefer a hardware problem, but I don't think. I have tested
 > | > | memory (16 GB ECC), swapped memory with another server last sunday
 > | > | without any result. I have to add that this issue only occurs when
 > | > | pkgsrc scripts runs 'make clean'.
 > | >
 > | > If it is ECC the it is probably not a problem. How easy is the problem to
 > | > reproduce? Is your kernel DIAGNOSTIC/DEBUG/LOCKDEBUG?
 > | >
 > | > christos
 > | >
 > |
 > | 	As I was not able to use altqd without panic, this server now runs with
 > | a GENERIC kernel (maybe DIAGNOSTIC is set, but not DEBUG/LOCKDEBUG).
 > | Don't forget this server is far away.
 > |
 > | 	I've never seen this trouble on slow CPU, but this server runs on a
 > | i7-4770 and I can reproduce this bug without any difficulties.
 >
 > If it is panicing with DEBUG/LOCKDEBUG altqd will never work properly...
 > Although improbably, it could be causing problems with the disk subsystem
 > too. Is it possible to turn off altq on it and see if the disk corruption
 > persists?
 >
 > christos
 
 	Since I have disabled altqd, my server runs now with a GENERIC kernel 
 that doesn't contain ALTQD (and not with my customized kernel).
 
 	Best regards,
 
 	JKB
 
 


Home | Main Index | Thread Index | Old Index