NetBSD-Bugs archive

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

Re: kern/47748: Invalid file on ffs



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

From: christos%zoulas.com@localhost (Christos Zoulas)
To: 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/47748: Invalid file on ffs
Date: Thu, 18 Apr 2013 09:45:44 -0400

 On Apr 18,  7:45am, frederic%fauberteau.org@localhost 
(frederic%fauberteau.org@localhost) wrote:
 -- Subject: kern/47748: Invalid file on ffs
 
 | >Number:         47748
 | >Category:       kern
 | >Synopsis:       Invalid file on ffs
 | >Confidential:   no
 | >Severity:       serious
 | >Priority:       high
 | >Responsible:    kern-bug-people
 | >State:          open
 | >Class:          sw-bug
 | >Submitter-Id:   net
 | >Arrival-Date:   Thu Apr 18 07:45:01 +0000 2013
 | >Originator:     Frédéric Fauberteau
 | >Release:        netbsd-6
 | >Organization:
 | >Environment:
 | NetBSD trashware 6.0_STABLE NetBSD 6.0_STABLE (TRASHWARE) #0: Fri Feb  8 
09:00:00 CET 2013  root@trashware:/usr/obj/sys/arch/amd64/compile/TRASHWARE 
amd64
 | >Description:
 | An invalid file is in the directory tree and can not be removed.
 | 
 | The report of daily insecurity script is:
 | Checking setuid files and devices:
 | Setuid/device find errors:
 | find: /usr/pkgsrc/ham/tfkiss/pkg/CVS/K+: No such file or directory
 | find: fts_read: No such file or directory
 | 
 | When I use autocomplete to try to remove the file, I obtain:
 | root@trashware:~$ rm /usr/pkgsrc/ham/tfkiss/pkg/CVS/K+^F
 | rm: /usr/pkgsrc/ham/tfkiss/pkg/CVS/K+: No such file or directory
 | 
 | root@trashware:pkg$ rm -rf /usr/pkgsrc/ham/tfkiss/pkg/CVS/
 | rm: CVS: Directory not empty
 | >How-To-Repeat:
 | No repeatable...
 | 
 | The file has probably been created by a failed ^C during a cvs update. The 
'F' key is very closed to the 'C' key, but I don't know the exact combination.
 
 fsck -f should be able to fix it, and if not there is always fsdb/clri
 
 christos
 


Home | Main Index | Thread Index | Old Index