NetBSD Problem Report #50707
From www@NetBSD.org Mon Jan 25 21:59:28 2016
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.NetBSD.org [199.233.217.200])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
by mollari.NetBSD.org (Postfix) with ESMTPS id 2A06C7A20D
for <gnats-bugs@gnats.NetBSD.org>; Mon, 25 Jan 2016 21:59:28 +0000 (UTC)
Message-Id: <20160125215925.EB6397ACAC@mollari.NetBSD.org>
Date: Mon, 25 Jan 2016 21:59:25 +0000 (UTC)
From: joel.bertrand@systella.fr
Reply-To: joel.bertrand@systella.fr
To: gnats-bugs@NetBSD.org
Subject: rm: fts_read: No such file or directory
X-Send-Pr-Version: www-1.0
>Number: 50707
>Category: kern
>Synopsis: rm: fts_read: No such file or directory
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Jan 25 22:00:00 +0000 2016
>Last-Modified: Sun Jul 09 12:30:01 +0000 2017
>Originator: BERTRAND Joël
>Release: NetBSD 7.0_STABLE (GENERIC.201512202240Z)
>Organization:
>Environment:
NetBSD legendre.systella.fr 7.0_STABLE NetBSD 7.0_STABLE (GENERIC.201512202240Z) amd64
>Description:
Hello,
I see on a NetBSD 7.0 server/amd64 a bug that is very similar to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192490
I've only seen this bug when I have tried to upgrade pkg from sources with pkg_rolling-replace but I think this issue can be triggered by some other programs.
pkg_rolling-replace -u often aborts with :
===> Cleaning for xxxxx
rm: fts_read: No such file or directory
*** Error code 1
If I try to remove work directory with rm -rvi work, I obtain :
remove 'work'? y
remove 'work/.buildlink'? y
remove 'work/.buildlink/include'? y
remove 'work/.buildlink/include/boost'? y
remove 'work/.buildlink/include/boost/interprocess'? y
remove 'work/.buildlink/include/boost/interprocess/mem_algo'? y
remove 'work/.buildlink/include/boost/interprocess/mem_algo/'? y
rm: work/.buildlink/include/boost/interprocess/mem_algo/: No such file or directory
rm: fts_read: No such file or directory
This slice contains a ffsv2 filesystem. I have tried with or without log with the same result.
Only one solution to fix this issue:
- reboot server in single user mode;
- execute a fsck on faulty filesystem.
A fsck returns :
legendre# fsck -f raid0e
** /dev/rraid0e
** File system is already clean
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
UNALLOCATED I=5313299 OWNER=0 MODE=0
SIZE=0 MTIME=Jan 25 00:40 2016
NAME=/pkgsrc/misc/kbruch/work/.buildlink/include/boost/interprocess/mem_algo/rbtree_best_fit.hpp
REMOVE? [yn] y
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
1088584 files, 10599592 used, 21929557 free (13949 frags, 2739451 blocks, 0.0% fragmentation)
***** FILE SYSTEM WAS MODIFIED *****
Each time, fsck claims about unallocated inode or partially allocated directory.
>How-To-Repeat:
With following /etc/mk.conf
ACCEPTABLE_LICENSES+= vim-license lame-license flash-license
MAKE_JOBS=8
ALLOW_VULNERABLE_PACKAGES= YES
only try to keep pkgsrc up to date with pkg_rolling-replace -u.
>Fix:
>Audit-Trail:
From: christos@zoulas.com (Christos Zoulas)
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Mon, 25 Jan 2016 17:02:15 -0500
On Jan 25, 10:00pm, joel.bertrand@systella.fr (joel.bertrand@systella.fr) wrote:
-- Subject: kern/50707: rm: fts_read: No such file or directory
Are you using log (WAPBL) with this filesystem?
christos
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Mon, 25 Jan 2016 23:19:11 +0100
Christos Zoulas a écrit :
> The following reply was made to PR kern/50707; it has been noted by GNATS.
>
> From: christos@zoulas.com (Christos Zoulas)
> To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
> gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> Cc:
> Subject: Re: kern/50707: rm: fts_read: No such file or directory
> Date: Mon, 25 Jan 2016 17:02:15 -0500
>
> On Jan 25, 10:00pm, joel.bertrand@systella.fr (joel.bertrand@systella.fr) wrote:
> -- Subject: kern/50707: rm: fts_read: No such file or directory
>
> Are you using log (WAPBL) with this filesystem?
I have tried with or without WAPBL with the same result. As I've never
seen this issue on sparc64 (FC-AL disks with raidframe), I have
suspected in a first time ataraid. Thus I have moved my ataraid
configuration to a new raidframe configuration (raid1) and I've seen
this issue again.
Thus with or without log, on ataraid or raidframe, system can corrupt a
ffsv2 slice. I haven't tested with other filesystems like lfs or without
raid.
Regards,
JKB
From: christos@zoulas.com (Christos Zoulas)
To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Mon, 25 Jan 2016 17:25:06 -0500
On Jan 25, 11:19pm, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
-- Subject: 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 (Christos Zoulas)
| > To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
| > gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
| > Cc:
| > Subject: Re: kern/50707: rm: fts_read: No such file or directory
| > Date: Mon, 25 Jan 2016 17:02:15 -0500
| >
| > On Jan 25, 10:00pm, joel.bertrand@systella.fr (joel.bertrand@systella.fr) wrote:
| > -- Subject: kern/50707: rm: fts_read: No such file or directory
| >
| > Are you using log (WAPBL) with this filesystem?
|
| I have tried with or without WAPBL with the same result. As I've never
| seen this issue on sparc64 (FC-AL disks with raidframe), I have
| suspected in a first time ataraid. Thus I have moved my ataraid
| configuration to a new raidframe configuration (raid1) and I've seen
| this issue again.
|
| Thus with or without log, on ataraid or raidframe, system can corrupt a
| ffsv2 slice. I haven't tested with other filesystems like lfs or without
| raid.
I am running with raidframe. Perhaps the problem is hardware. I would check
the memory... The disks being at fault is less likely with raidframe.
christos
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: Christos Zoulas <christos@zoulas.com>, gnats-bugs@NetBSD.org,
kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Mon, 25 Jan 2016 23:35:36 +0100
Christos Zoulas a écrit :
> On Jan 25, 11:19pm, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
> -- Subject: 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 (Christos Zoulas)
> | > To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
> | > gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> | > Cc:
> | > Subject: Re: kern/50707: rm: fts_read: No such file or directory
> | > Date: Mon, 25 Jan 2016 17:02:15 -0500
> | >
> | > On Jan 25, 10:00pm, joel.bertrand@systella.fr (joel.bertrand@systella.fr) wrote:
> | > -- Subject: kern/50707: rm: fts_read: No such file or directory
> | >
> | > Are you using log (WAPBL) with this filesystem?
> |
> | I have tried with or without WAPBL with the same result. As I've never
> | seen this issue on sparc64 (FC-AL disks with raidframe), I have
> | suspected in a first time ataraid. Thus I have moved my ataraid
> | configuration to a new raidframe configuration (raid1) and I've seen
> | this issue again.
> |
> | Thus with or without log, on ataraid or raidframe, system can corrupt a
> | ffsv2 slice. I haven't tested with other filesystems like lfs or without
> | raid.
>
> I am running with raidframe. Perhaps the problem is hardware. I would check
> the memory... The disks being at fault is less likely with raidframe.
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'.
Regards,
JKB
From: christos@zoulas.com (Christos Zoulas)
To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Mon, 25 Jan 2016 19:02:02 -0500
On Jan 25, 11:35pm, joel.bertrand@systella.fr (=?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
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: Christos Zoulas <christos@zoulas.com>, gnats-bugs@NetBSD.org,
kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Tue, 26 Jan 2016 08:37:46 +0100
Christos Zoulas a écrit :
> On Jan 25, 11:35pm, joel.bertrand@systella.fr (=?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.
Best regards,
JKB
From: christos@zoulas.com (Christos Zoulas)
To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Tue, 26 Jan 2016 08:47:26 -0500
On Jan 26, 8:37am, joel.bertrand@systella.fr (=?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 (=?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
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: Christos Zoulas <christos@zoulas.com>, gnats-bugs@NetBSD.org,
kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org
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 (=?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 (=?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
From: christos@zoulas.com (Christos Zoulas)
To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
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 (=?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
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Tue, 26 Jan 2016 15:09:51 +0100
Christos Zoulas a écrit :
> The following reply was made to PR kern/50707; it has been noted by GNATS.
>
> From: christos@zoulas.com (Christos Zoulas)
> To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
> gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
> gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
> 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 (=?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
From: christos@zoulas.com (Christos Zoulas)
To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Tue, 26 Jan 2016 10:26:08 -0500
On Jan 26, 3:09pm, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
-- Subject: Re: kern/50707: rm: fts_read: No such file or directory
| I cannot activate debug options as this server is far away and I won't
| have a console access before a couple of weeks.
While this bug is similar with FreeBSDs it is different because it does not
look like FreeBSDs causes filesystem corruption. Nevertheless I will try
to reproduce it here..
christos
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Tue, 26 Apr 2016 11:44:57 +0200
Christos Zoulas a écrit :
> The following reply was made to PR kern/50707; it has been noted by GNATS.
>
> From: christos@zoulas.com (Christos Zoulas)
> To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
> gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
> gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
> Cc:
> Subject: Re: kern/50707: rm: fts_read: No such file or directory
> Date: Tue, 26 Jan 2016 10:26:08 -0500
>
> On Jan 26, 3:09pm, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
> -- Subject: Re: kern/50707: rm: fts_read: No such file or directory
>
> | I cannot activate debug options as this server is far away and I won't
> | have a console access before a couple of weeks.
>
> While this bug is similar with FreeBSDs it is different because it does not
> look like FreeBSDs causes filesystem corruption. Nevertheless I will try
> to reproduce it here..
>
> christos
>
>
Hello Christos,
Have you reproduced this bug ? I have seen another corruption this
morning (NetBSD 7_0 Patch) when I have tried to build seamonkey. mount
-ur -f /usr refuses to remount /usr in readonly to run fsck...
Best regards,
JKB
From: christos@zoulas.com (Christos Zoulas)
To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Tue, 26 Apr 2016 08:41:27 -0400
On Apr 26, 11:44am, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
-- Subject: Re: kern/50707: rm: fts_read: No such file or directory
| Hello Christos,
|
| Have you reproduced this bug ? I have seen another corruption this
| morning (NetBSD 7_0 Patch) when I have tried to build seamonkey. mount
| -ur -f /usr refuses to remount /usr in readonly to run fsck...
|
You don't need to mount to run fsck... fsck'ing a mounted filesystem will
corrupt it.
christos
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Tue, 26 Apr 2016 15:17:47 +0200
Christos Zoulas a écrit :
> The following reply was made to PR kern/50707; it has been noted by GNATS.
>
> From: christos@zoulas.com (Christos Zoulas)
> To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
> gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
> gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
> Cc:
> Subject: Re: kern/50707: rm: fts_read: No such file or directory
> Date: Tue, 26 Apr 2016 08:41:27 -0400
>
> On Apr 26, 11:44am, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
> -- Subject: Re: kern/50707: rm: fts_read: No such file or directory
>
> | Hello Christos,
> |
> | Have you reproduced this bug ? I have seen another corruption this
> | morning (NetBSD 7_0 Patch) when I have tried to build seamonkey. mount
> | -ur -f /usr refuses to remount /usr in readonly to run fsck...
> |
>
> You don't need to mount to run fsck... fsck'ing a mounted filesystem will
> corrupt it.
I know. But I try to _re_mount /usr in readonly mode to run fsck
without rebooting my server...
Regards,
JKB
From: Robert Elz <kre@munnari.OZ.AU>
To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
Cc: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Tue, 26 Apr 2016 21:36:10 +0700
Date: Tue, 26 Apr 2016 15:17:47 +0200
From: =3D?UTF-8?Q?BERTRAND_Jo=3Dc3=3Dabl?=3D <joel.bertrand=40=
systella.fr>
Message-ID: <571F6A7B.7060402=40systella.fr>
=7C I know. But I try to _re_mount /usr in readonly mode to run fsck=20
=7C without rebooting my server...
NetBSD does not currently support moving from read-write to read only,
you need to boot with the file system in read only mode (you can switch
to read-write later if you need to.)
I have a patch you can apply that will allow switching to read-only mode,=
but you do need to be very careful - the ability to do that was removed
because it does not always work correctly, to switch to read-only mode ta=
kes
some care to make sure the filesystem is in a suitable state first (the
system should simply make it work, but no-one ever found out why it didn'=
t.)
kre
From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Mon, 30 May 2016 03:40:41 +0000
On Tue, Apr 26, 2016 at 02:40:01PM +0000, Robert Elz wrote:
> I have a patch you can apply that will allow switching to
> read-only mode, but you do need to be very careful - the ability to
> do that was removed because it does not always work correctly, to
> switch to read-only mode takes some care to make sure the
> filesystem is in a suitable state first (the system should simply
> make it work, but no-one ever found out why it didn't.)
Well, that's not quite true. We found one at least one set of
problems, which is that the logic for delayed mtime/atime updates was
not pushing pending mtime/atime updates out. That I believe has been
fixed.
There was also another set of problems that came to light when someone
discovered that -o async wasn't ever writing anything out at all
unless forced to by buffer cache capacity, but I don't remember what
the resolution of that was, if any.
--
David A. Holland
dholland@netbsd.org
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Mon, 6 Jun 2016 11:31:48 +0200
David Holland a écrit :
> The following reply was made to PR kern/50707; it has been noted by GNATS.
>
> From: David Holland <dholland-bugs@netbsd.org>
> To: gnats-bugs@NetBSD.org
> Cc:
> Subject: Re: kern/50707: rm: fts_read: No such file or directory
> Date: Mon, 30 May 2016 03:40:41 +0000
>
> On Tue, Apr 26, 2016 at 02:40:01PM +0000, Robert Elz wrote:
> > I have a patch you can apply that will allow switching to
> > read-only mode, but you do need to be very careful - the ability to
> > do that was removed because it does not always work correctly, to
> > switch to read-only mode takes some care to make sure the
> > filesystem is in a suitable state first (the system should simply
> > make it work, but no-one ever found out why it didn't.)
>
> Well, that's not quite true. We found one at least one set of
> problems, which is that the logic for delayed mtime/atime updates was
> not pushing pending mtime/atime updates out. That I believe has been
> fixed.
>
> There was also another set of problems that came to light when someone
> discovered that -o async wasn't ever writing anything out at all
> unless forced to by buffer cache capacity, but I don't remember what
> the resolution of that was, if any.
>
> --
> David A. Holland
> dholland@netbsd.org
>
>
Hello,
I have applied last patches. Now, my server runs 7.0.1. Last night,
after upgrading pkgsrc from CVS tree, I have seen "to many open files"
and fs was currupted again. Some directories do not contains '.' or '..'.
legendre$ uname -a
NetBSD legendre.systella.fr 7.0.1 NetBSD 7.0.1 (GENERIC.201605221355Z) amd64
legendre$ mount
/dev/raid0a on / type ffs (asynchronous, log, NFS exported, local)
/dev/raid0f on /var type ffs (asynchronous, log, local)
/dev/raid0e on /usr type ffs (local)
/dev/raid0g on /home type ffs (asynchronous, log, NFS exported, local)
kernfs on /kern type kernfs (local)
ptyfs on /dev/pts type ptyfs (local)
procfs on /proc type procfs (local)
tmpfs on /var/shm type tmpfs (local)
legendre$
If I remove async from /etc/fstab, I obtain a fts_read error. With
aync, error differs but result is the same. I have to reboot with fs in
ro mode to run fsck.
Best regards,
JKB
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Thu, 23 Jun 2016 20:33:21 +0200
BERTRAND Joël a écrit :
> 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>
> To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
> netbsd-bugs@netbsd.org
> Cc:
> Subject: Re: kern/50707: rm: fts_read: No such file or directory
> Date: Mon, 6 Jun 2016 11:31:48 +0200
>
> David Holland a écrit :
> > The following reply was made to PR kern/50707; it has been noted by GNATS.
> >
> > From: David Holland <dholland-bugs@netbsd.org>
> > To: gnats-bugs@NetBSD.org
> > Cc:
> > Subject: Re: kern/50707: rm: fts_read: No such file or directory
> > Date: Mon, 30 May 2016 03:40:41 +0000
> >
> > On Tue, Apr 26, 2016 at 02:40:01PM +0000, Robert Elz wrote:
> > > I have a patch you can apply that will allow switching to
> > > read-only mode, but you do need to be very careful - the ability to
> > > do that was removed because it does not always work correctly, to
> > > switch to read-only mode takes some care to make sure the
> > > filesystem is in a suitable state first (the system should simply
> > > make it work, but no-one ever found out why it didn't.)
> >
> > Well, that's not quite true. We found one at least one set of
> > problems, which is that the logic for delayed mtime/atime updates was
> > not pushing pending mtime/atime updates out. That I believe has been
> > fixed.
> >
> > There was also another set of problems that came to light when someone
> > discovered that -o async wasn't ever writing anything out at all
> > unless forced to by buffer cache capacity, but I don't remember what
> > the resolution of that was, if any.
> >
> > --
> > David A. Holland
> > dholland@netbsd.org
> >
> >
>
> Hello,
>
> I have applied last patches. Now, my server runs 7.0.1. Last night,
> after upgrading pkgsrc from CVS tree, I have seen "to many open files"
> and fs was currupted again. Some directories do not contains '.' or '..'.
>
> legendre$ uname -a
> NetBSD legendre.systella.fr 7.0.1 NetBSD 7.0.1 (GENERIC.201605221355Z) amd64
> legendre$ mount
> /dev/raid0a on / type ffs (asynchronous, log, NFS exported, local)
> /dev/raid0f on /var type ffs (asynchronous, log, local)
> /dev/raid0e on /usr type ffs (local)
> /dev/raid0g on /home type ffs (asynchronous, log, NFS exported, local)
> kernfs on /kern type kernfs (local)
> ptyfs on /dev/pts type ptyfs (local)
> procfs on /proc type procfs (local)
> tmpfs on /var/shm type tmpfs (local)
> legendre$
>
> If I remove async from /etc/fstab, I obtain a fts_read error. With
> aync, error differs but result is the same. I have to reboot with fs in
> ro mode to run fsck.
>
> Best regards,
>
> JKB
>
>
Hello,
Any news ? I have seen some other disk corruption since my last
message... I can do some tests but I don't know VFS subsystem enough to
debug.
Best regards,
JKB
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: Brad Spencer <brad@anduin.eldar.org>, kern-bug-people@NetBSD.org,
gnats-bugs@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Fri, 24 Jun 2016 07:56:12 +0200
Brad Spencer a écrit :
> BERTRAND Joël <joel.bertrand@systella.fr> writes:
>
> [snip]
>
>> Hello,
>>
>> Any news ? I have seen some other disk corruption since my last
>> message... I can do some tests but I don't know VFS subsystem enough to
>> debug.
>>
>> Best regards,
>>
>> JKB
>
>
> Hello.... I have a curious question for you, and forgive me if you have
> answered it already. Did you use resize_ffs at any time on the
> filesystem that has corruption??
>
>
>
Hello,
I haven't use resize_ffs on this server.
Best regards,
JKB
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Mon, 27 Jun 2016 09:10:28 +0200
Some news.
Last saturday, I have tried to bissect fts code without any success,
but I have seen that disk corruption only occurs on high disk I/O (for
example make clean in ports tree, I use MAKE_JOBS=8 as this server
contains an i7 CPU with 8 threads). All disk corruptions are directories
without '.'. fsck returns that directories were 'half allocated'.
Best regards,
JKB
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Tue, 5 Jul 2016 09:59:25 +0200
BERTRAND Joël a écrit :
> 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>
> To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
> netbsd-bugs@netbsd.org
> Cc:
> Subject: Re: kern/50707: rm: fts_read: No such file or directory
> Date: Mon, 27 Jun 2016 09:10:28 +0200
>
> Some news.
>
> Last saturday, I have tried to bissect fts code without any success,
> but I have seen that disk corruption only occurs on high disk I/O (for
> example make clean in ports tree, I use MAKE_JOBS=8 as this server
> contains an i7 CPU with 8 threads). All disk corruptions are directories
> without '.'. fsck returns that directories were 'half allocated'.
>
> Best regards,
>
> JKB
>
>
Hello,
Another one, but without any 'rm'. This morning, I have received a mail
from Charlie root :
daily insecurity output for Tue Jul 5 03:15:01 CEST 2016
Checking setuid files and devices:
Setuid/device find errors:
find: fts_read: No such file or directory
I wonder if this issue could be related to disk internal cache
strategy. Now, both disks return :
legendre# legendre# dkctl /dev/wd1 getcache
/dev/wd1d: read cache enabled
/dev/wd1d: write-back cache enabled
/dev/wd1d: read cache enable is not changeable
/dev/wd1d: write cache enable is changeable
/dev/wd1d: cache parameters are not savable
legendre# dkctl /dev/wd0 getcache
/dev/wd0d: read cache enabled
/dev/wd0d: write-back cache enabled
/dev/wd0d: read cache enable is not changeable
/dev/wd0d: write cache enable is changeable
/dev/wd0d: cache parameters are not savable
legendre#
Is there a hope to fix this particularly bad issue ?
Best regards,
JKB
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org,
"NetBSD Users's Discussion List" <netbsd-users@NetBSD.org>
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Fri, 5 Aug 2016 09:14:28 +0200
BERTRAND Joël a écrit :
> 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>
> To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
> netbsd-bugs@netbsd.org
> Cc:
> Subject: Re: kern/50707: rm: fts_read: No such file or directory
> Date: Tue, 5 Jul 2016 09:59:25 +0200
>
> BERTRAND Joël a écrit :
> > 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>
> > To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
> > netbsd-bugs@netbsd.org
> > Cc:
> > Subject: Re: kern/50707: rm: fts_read: No such file or directory
> > Date: Mon, 27 Jun 2016 09:10:28 +0200
> >
> > Some news.
> >
> > Last saturday, I have tried to bissect fts code without any success,
> > but I have seen that disk corruption only occurs on high disk I/O (for
> > example make clean in ports tree, I use MAKE_JOBS=8 as this server
> > contains an i7 CPU with 8 threads). All disk corruptions are directories
> > without '.'. fsck returns that directories were 'half allocated'.
> >
> > Best regards,
> >
> > JKB
> >
> >
>
> Hello,
>
> Another one, but without any 'rm'. This morning, I have received a mail
> from Charlie root :
>
> daily insecurity output for Tue Jul 5 03:15:01 CEST 2016
> Checking setuid files and devices:
> Setuid/device find errors:
> find: fts_read: No such file or directory
>
> I wonder if this issue could be related to disk internal cache
> strategy. Now, both disks return :
> legendre# legendre# dkctl /dev/wd1 getcache
> /dev/wd1d: read cache enabled
> /dev/wd1d: write-back cache enabled
> /dev/wd1d: read cache enable is not changeable
> /dev/wd1d: write cache enable is changeable
> /dev/wd1d: cache parameters are not savable
> legendre# dkctl /dev/wd0 getcache
> /dev/wd0d: read cache enabled
> /dev/wd0d: write-back cache enabled
> /dev/wd0d: read cache enable is not changeable
> /dev/wd0d: write cache enable is changeable
> /dev/wd0d: cache parameters are not savable
> legendre#
>
> Is there a hope to fix this particularly bad issue ?
>
> Best regards,
>
> JKB
>
>
Hello,
Some news. Last night, kernel panics with :
/: bad dir ino 2130825 at offset 0: mangled entry
panic: bad dir
cpu5: Begin traceback...
vpanic() at netbsd:vpanic+0x13c
snprintf() at netbsd:snprintf
ufs_dirbadentry() at netbsd:ufs_dirbadentry
ufs_lookup() at netbsd:ufs_lookup+0x4c3
VOP_LOOKUP() at netbsd:VOP_LOOKUP+0x34
lookup_once() at netbsd:lookup_once+0x18b
namei_tryemulroot() at netbsd:namei_tryemulroot+0x612
namei() at netbsd:namei+0x43
fd_nameiat.isra.0() at netbsd:fd_nameiat.isra.0+0x54
do_sys_statat() at netbsd:do_sys_statat+0x72
sys___lstat50() at netbsd:sys___lstat50+0x25
syscall() at netbsd:syscall+0x9a
--- syscall (number 441) ---
7f7ff70a705a:
cpu5: End traceback...
uvm_fault(0xfffffe83b899b760, 0x0, 2) -> e
uvm_fault(0xfffffe840f88e310, 0x0, 2) -> e
fatal page fault in supervisor mode
fatal page fault in supervisotrr ampo dtey
pe 6 code 2 rip ffffffff805db5b9 cs 8 rflags 10202 cr2 84 ilevel 8 rsp
fffffe812108fb98
trap type 6 code 2 rip ffffffff805db5b9 cs 8 rflags 10202 cr2 84 ilevel
8 rsp ffcfufrflew8p1 2102xf3f4fbfaf8e
83ea9c8200 pid 20893.3 lowest kstack 0xfffffe812108d2c0
dumping to dev 18,1 (offset=251903, size=4162816):
curlwp 0xfffffe83dcdc6440 pid 2611.7 lowest kstack 0xfffffe81212322c0
I suppose this panic is related to tfs error I have seen. I'm pretty
sure that this server doesn't have harware issue (disks smart parameters
are corrects and I have checked these disks in another workstation).
For information, boths disks are :
Device Model: TOSHIBA DT01ACA100
Regards,
JKB
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Fri, 19 Aug 2016 09:08:38 +0200
Hello,
I have replaced disks by new ones with the same result. Under high I/O,
system panics with :
/: bad dir ino 2130825 at offset 0: mangled entry
panic: bad dir
cpu1: Begin traceback...
vpanic() at netbsd:vpanic+0x13c
snprintf() at netbsd:snprintf
ufs_dirbadentry() at netbsd:ufs_dirbadentry
ufs_lookup() at netbsd:ufs_lookup+0x4c3
VOP_LOOKUP() at netbsd:VOP_LOOKUP+0x34
lookup_once() at netbsd:lookup_once+0x18b
namei_tryemulroot() at netbsd:namei_tryemulroot+0x612
namei() at netbsd:namei+0x43
fd_nameiat.isra.0() at netbsd:fd_nameiat.isra.0+0x54
do_sys_statat() at netbsd:do_sys_statat+0x72
sys___lstat50() at netbsd:sys___lstat50+0x25
syscall() at netbsd:syscall+0x9a
--- syscall (number 441) ---
7f7ff70a705a:
cpu1: End traceback...
System runs NetBSD 7.0.1 stable. In last panic (5th of august), kernel
complains about :
/: bad dir ino 2130825 at offset 0: mangled entry
In this panic, it complains about the same bad dir inode. But fsck
doesn't return any error.
I can upload somewhere netbsd.core.gz and netbsd.gz. I don't know how
debug this issue.
Best regards,
JKB
From: christos@zoulas.com (Christos Zoulas)
To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Fri, 19 Aug 2016 05:25:12 -0400
On Aug 19, 9:08am, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
-- Subject: Re: kern/50707: rm: fts_read: No such file or directory
| Hello,
|
| I have replaced disks by new ones with the same result. Under high I/O,
| system panics with :
|
| /: bad dir ino 2130825 at offset 0: mangled entry
| panic: bad dir
| cpu1: Begin traceback...
| vpanic() at netbsd:vpanic+0x13c
| snprintf() at netbsd:snprintf
| ufs_dirbadentry() at netbsd:ufs_dirbadentry
| ufs_lookup() at netbsd:ufs_lookup+0x4c3
| VOP_LOOKUP() at netbsd:VOP_LOOKUP+0x34
| lookup_once() at netbsd:lookup_once+0x18b
| namei_tryemulroot() at netbsd:namei_tryemulroot+0x612
| namei() at netbsd:namei+0x43
| fd_nameiat.isra.0() at netbsd:fd_nameiat.isra.0+0x54
| do_sys_statat() at netbsd:do_sys_statat+0x72
| sys___lstat50() at netbsd:sys___lstat50+0x25
| syscall() at netbsd:syscall+0x9a
| --- syscall (number 441) ---
| 7f7ff70a705a:
| cpu1: End traceback...
|
| System runs NetBSD 7.0.1 stable. In last panic (5th of august), kernel
| complains about :
| /: bad dir ino 2130825 at offset 0: mangled entry
Is this ffsv2?
christos
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Fri, 19 Aug 2016 13:18:46 +0200
Christos Zoulas a écrit :
> Is this ffsv2?
Yes, it is. All my fs are ffsv2 on this server.
Best regards,
JKB
From: christos@zoulas.com (Christos Zoulas)
To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Fri, 19 Aug 2016 07:44:43 -0400
On Aug 19, 1:18pm, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
-- Subject: Re: kern/50707: rm: fts_read: No such file or directory
| Christos Zoulas a écrit :
| > Is this ffsv2?
Can you put a current kernel on the machine and see if it still crashes?
christos
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Fri, 19 Aug 2016 18:14:20 +0200
Christos Zoulas a écrit :
> The following reply was made to PR kern/50707; it has been noted by GNATS.
>
> From: christos@zoulas.com (Christos Zoulas)
> To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
> gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
> gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> Cc:
> Subject: Re: kern/50707: rm: fts_read: No such file or directory
> Date: Fri, 19 Aug 2016 07:44:43 -0400
>
> On Aug 19, 1:18pm, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
> -- Subject: Re: kern/50707: rm: fts_read: No such file or directory
>
> | Christos Zoulas a écrit :
> | > Is this ffsv2?
>
> Can you put a current kernel on the machine and see if it still crashes?
>
> christos
>
>
I'm building a current kernel. If I remember, I have tried with 7.99.25
and I obtained the same error.
Regards,
JKB
From: christos@zoulas.com (Christos Zoulas)
To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Fri, 19 Aug 2016 12:49:55 -0400
On Aug 19, 6:14pm, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
-- Subject: Re: kern/50707: rm: fts_read: No such file or directory
| I'm building a current kernel. If I remember, I have tried with 7.99.25
| and I obtained the same error.
Is there anything particular with your workload?
How many processors/memory does you machine have?
christos
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: Christos Zoulas <christos@zoulas.com>, gnats-bugs@NetBSD.org,
kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Fri, 19 Aug 2016 19:56:08 +0200
Christos Zoulas a écrit :
> On Aug 19, 6:14pm, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
> -- Subject: Re: kern/50707: rm: fts_read: No such file or directory
>
> | I'm building a current kernel. If I remember, I have tried with 7.99.25
> | and I obtained the same error.
>
> Is there anything particular with your workload?
> How many processors/memory does you machine have?
>
> christos
>
16 GB
i7-4770 on Asus Motherboard.
System can panic with a simple cvs update of NetBSD tree.
legendre$ df -h
Filesystem Size Used Avail %Cap Mounted on
/dev/raid0a 31G 7.9G 22G 26% /
/dev/raid0f 31G 3.7G 26G 12% /var
/dev/raid0e 62G 9.7G 49G 16% /usr
/dev/raid0g 252G 12G 228G 4% /usr/src
/dev/raid0h 523G 29G 468G 5% /srv
/dev/dk0 3.6T 132G 3.3T 3% /home
kernfs 1.0K 1.0K 0B 100% /kern
ptyfs 1.0K 1.0K 0B 100% /dev/pts
procfs 4.0K 4.0K 0B 100% /proc
tmpfs 4.0G 24K 4.0G 0% /var/shm
legendre#
I have tried last current kernel but it sometimes panics with :
uvm_fault(0xfffffe81767695c8, 0x0, 1) -> e
fatal page fault in supervisor mode
trap type 6 code 0 rip ffffffff808ab397 cs 8 rflags 10286 cr2 8 ilevel 0
rsp fffffe811ed2eb80
curlwp 0xfffffe84150be720 pid 97.1 lowest kstack 0xfffffe811ed2b2c0
panic: trap
cpu1: Begin traceback...
vpanic() at netbsd:vpanic+0x140
snprintf() at netbsd:snprintf
trap() at netbsd:trap+0xc4b
--- trap (number 6) ---
filt_sowdetach() at netbsd:filt_sowdetach+0x3f
knote_detach() at netbsd:knote_detach+0x70
kevent1() at netbsd:kevent1+0x686
sys___kevent50() at netbsd:sys___kevent50+0x33
syscall() at netbsd:syscall+0x15b
--- syscall (number 435) ---
70490023c54a:
cpu1: End traceback...
Regards,
JKB
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Sun, 9 Jul 2017 14:28:06 +0200
Christos Zoulas a écrit :
> The following reply was made to PR kern/50707; it has been noted by GNATS.
>
> From: christos@zoulas.com (Christos Zoulas)
> To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>,
> gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
> gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> Cc:
> Subject: Re: kern/50707: rm: fts_read: No such file or directory
> Date: Fri, 19 Aug 2016 12:49:55 -0400
>
> On Aug 19, 6:14pm, joel.bertrand@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
> -- Subject: Re: kern/50707: rm: fts_read: No such file or directory
>
> | I'm building a current kernel. If I remember, I have tried with 7.99.25
> | and I obtained the same error.
>
> Is there anything particular with your workload?
> How many processors/memory does you machine have?
>
> christos
>
>
Hello,
If this issue seems to be fixed in 7.0.1 and 7.0.2, I doesn't in
8.0_BETA. For one week I test 8.0_BETA, I see lot of fts_read errors :
./share/ri/2.3.0/system/RSS
./share/ri/2.3.0/system/RSS/Atom
./share/ri/2.3.0/system/RSS/Atom/CommonModel
./share/ri/2.3.0/system/RSS/Atom/CommonModel/
find: fts_read: No such file or directory
legendre# cd ./share/ri/2.3.0/system/RSS/Atom/CommonModel/
/usr/pkg/share/ri/2.3.0/system/RSS/Atom/CommonModel
legendre# ls
ls: .: No such file or directory
Best regards,
JKB
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2014
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home