Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Apr 2014 15:12:45 -0700
From:      Garrett Cooper <yaneurabeya@gmail.com>
To:        Gary Palmer <gpalmer@freebsd.org>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: Immutable files on UFS?
Message-ID:  <CAGHfRMCPQU47u5oZ2x1Om_nY9C5EWKvRY2Pr-AbmmiPrHD0H2Q@mail.gmail.com>
In-Reply-To: <20140410220411.GB15884@in-addr.com>
References:  <CAGHfRMAxbUjiYY5WOtxQLZ=Wzwn25b1sHABwMg0VaCku5sXeRA@mail.gmail.com> <20140410220411.GB15884@in-addr.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Thu, Apr 10, 2014 at 3:04 PM, Gary Palmer <gpalmer@freebsd.org> wrote:

...

> Try looking at files in that directory with the '-o' flag to ls.  e.g.
>
> ls -lago /usr/obj~/usr/src/tmp/usr/lib/engines/

Thanks for the extra ls -l command (so many flags, so little time!).

> If you see files with 'schg' on them, then run

Unfortunately there aren't any. chflags -R 0 clears all of the chflags
on files. I always run that instead of running noschg nowadays on
directories like /usr/obj*, like buildworld does.

> chflags noschg <filename>
>
> You could also do
>
> chflags -PR noschg /usr/obj~/

Hmm... didn't try it without -P. According to the manpage it should be
the default, but it wasn't when I ran it. That solved my issue with
the pjdfstest file, but not /usr/obj~.

> although be careful, as some files on the filesystem (such as /lib/libc.so.*)
> are meant to be immutable.

Indeed :).

> If you are running with a securelevel above 0 the above won't be possible.

My kern.securelevel's unset :).

Thanks!
-Garrett



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