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



Christos Zoulas a écrit :
The following reply was made to PR kern/50707; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand%systella.fr@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 08:58:03 -0500

  On Jan 26,  2:50pm, 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

  | 	Since I have disabled altqd, my server runs now with a GENERIC kernel
  | that doesn't contain ALTQD (and not with my customized kernel).

  And you still see corruption? Also now that altq is gone, can you enable
  diagnostic debug and lockdebug. It really should not fail now... I suspect
  that the locking issue is with altq.

  christos


I don't see any relation between altqd and data corruption I see. I have disabled altqd since I have understand that it causes panics (exactly since my PR on altqd, Mon Jan 18 09:12:36 2016).

Thus, for one week, this server only runs on a GENERIC kernel (built by NetBSD team). It doesn't have ALTQD, nor DIAGNOSTIC, DEBUG or LOCKDEBUG. Data corruption only occurs when pkg_rolling-replace tries to run 'make clean' and this bug looks like FreeBSD's bug.

I cannot activate debug options as this server is far away and I won't have a console access before a couple of weeks.

	Regards,

	JKB


Home | Main Index | Thread Index | Old Index