Date: Tue, 6 Jun 1995 21:10:02 -0700 From: Heikki Suonsivu <hsu@clinet.fi> To: freebsd-bugs Subject: kern/495: Unremovable file? Message-ID: <199506070410.VAA29596@freefall.cdrom.com> In-Reply-To: Your message of Wed, 7 Jun 1995 07:08:43 %2B0300 <199506070408.HAA12334@katiska.clinet.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
>Number: 495 >Category: kern >Synopsis: Filesystem contains a file which is unremovable. >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jun 6 21:10:01 1995 >Originator: Heikki Suonsivu >Organization: Helsinki University of Technology, Finland >Release: FreeBSD 2.0-BUILT-19950507 i386 >Environment: FreeBSD running -current. P90, NNTP server + various other jobs. The file in question appeared on the news filesystem. >Description: hsu#katiska.clinet.fi Wed 68: ls -l .overview -rw-rw-r-- 1 news news 31939 May 9 07:38 .overview hsu#katiska.clinet.fi Wed 69: mv .overview foo mv: cannot move `.overview' to `foo': Operation not permitted hsu#katiska.clinet.fi Wed 70: L -d . drwxrwxr-x 2 news news 512 Jun 7 06:52 ./ hsu#katiska.clinet.fi Wed 71: chmod 777 . hsu#katiska.clinet.fi Wed 72: rm .overview rm: remove `.overview'? y rm: .overview: Operation not permitted hsu#katiska.clinet.fi Wed 73: L total 35 drwxrwxrwx 2 news news 512 Jun 7 06:52 ./ drwxr-xr-x 3 hsu wheel 1536 Jun 7 04:38 ../ -rw-rw-r-- 1 news news 31939 May 9 07:38 .overview hsu#katiska.clinet.fi Wed 74: L -d . drwxrwxrwx 2 news news 512 Jun 7 06:52 ./ hsu#katiska.clinet.fi Wed 75: df . Filesystem 1024-blocks Used Available Cap. Mounted on /dev/sd1g 1980569 1448498 433043 77% /m/katiska/news hsu#katiska.clinet.fi Wed 76: chmod 775 . hsu#katiska.clinet.fi Wed 77: pwd /m/katiska/news/tmp/guns-rikki Everything I do, it always says no permission (is there a FORCE option somewhere?) It stays over reboot or fsck. It cannot be renamed, but the directory it is in can be moved. I think I have seen a similar thing on NFS mounted file system, but the offending file could be removed from the NFS server. >How-To-Repeat: Don't know, but I can dig more info for someone who wants to look at it (the file is quite persistent so it is not going away :-) Just tell me what to look for. >Fix: These shouldn't be generated? fsck should be able to detect and remove these? That is, if it is a filesystem problem, not something else. All computer programs should have a --force or --I-know-what-I-am-doing option! >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506070410.VAA29596>