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