Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 4 Jun 2006 14:40:22 -0400
From:      Bill Moran <wmoran@collaborativefusion.com>
To:        "Jack Stone" <antennex@hotmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Cannot delete stubborn files
Message-ID:  <20060604144022.160fbc26.wmoran@collaborativefusion.com>
In-Reply-To: <BAY106-F18B37F868BCB9A7ABAE478CC970@phx.gbl>
References:  <20060604093513.X56404@tripel.monochrome.org> <BAY106-F18B37F868BCB9A7ABAE478CC970@phx.gbl>

next in thread | previous in thread | raw e-mail | index | archive | help
"Jack Stone" <antennex@hotmail.com> wrote:

> >From: Chris Hill <chris@monochrome.org>
> >To: Jack Stone <antennex@hotmail.com>
> >CC: freebsd-questions@freebsd.org
> >Subject: Re: Cannot delete stubborn files
> >Date: Sun, 4 Jun 2006 09:39:51 -0400 (EDT)
> >
> >On Sun, 4 Jun 2006, Jack Stone wrote:
> >
> >>I have 2 files that resists all efforts to delete them.
> >
> >[...]
> >
> >>Here are the files and the error message:
> >>rm: local/lib/perl5/5.6.1/mach/Sys/Hostname.pm: Operation not permitted
> >>rm: local/lib/perl5/5.6.1/mach/Sys/Syslog.pm: Operation not permitted
> >
> >Make sure the files do not have the system immutable flag set:
> >
> ># chflags noschg local/lib/perl5/5.6.1/mach/Sys/Hostname.pm
> ># chflags noschg local/lib/perl5/5.6.1/mach/Sys/Syslog.pm
> >
> >...and then see if you can't delete them. I don't know why the flag would 
> >be set, but it's something to try.
> >
> >HTH.
> >
> >--
> >Chris Hill               chris@monochrome.org
> 
> Chris: Tried that at the very first. No joy!

If flags and permissions are all set so that the files should delete, and
they still don't, reboot the system into single user mode and fsck the
partition.

I had this happen a number of years ago.  We had dirty power and the system
would reboot on occasion during brownout.  We finally got UPS on the system,
but months later we had files that wouldn't delete.  The only way we finally
got rid of them was to reboot in single user and fsck.  I expect the disk
suffered some subtle corruption during an unclean boot and it took time
before we noticed.

Another option would be to use fstat to make sure nothing has the files open.

HTH.

-- 
Bill Moran

Six men came to kill me one time, and the best of them carried this. It's
a Callahan fullbore autolock, customized trigger and double cartridge
thourough-gage.  It's my very favorite gun.

	Jayne Cobb




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060604144022.160fbc26.wmoran>