From owner-freebsd-fs@FreeBSD.ORG  Thu Apr 10 22:12:46 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 6C4B828A;
 Thu, 10 Apr 2014 22:12:46 +0000 (UTC)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com
 [IPv6:2607:f8b0:400c:c01::231])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 1AC241AC3;
 Thu, 10 Apr 2014 22:12:46 +0000 (UTC)
Received: by mail-ve0-f177.google.com with SMTP id sa20so3935028veb.22
 for <multiple recipients>; Thu, 10 Apr 2014 15:12:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=3VnLnER/P136Cg5ZhjWI5TfQivvr6pbClQEfAx0P0F0=;
 b=vrB66TegUTArdyVlcw6ogETGOaJ/MHV2Nz4R8QREQiiYOc67F/lN0OSnUyHWihB5OD
 TqublNzdfu6iv3bwRHVXLhfPt+tu2nwy5Qh4638/E4u7nhr4fdqPiZ+xbYA+tsCE4zeZ
 reBErpwIf7gT7BTYwwcReNIkUXWOt94aCadF9nyS2dM1IQ6hMR26hl658X2oCSa2hxva
 c8IdP9ggTSYe8JHYLF7bSwpdN17eq3iEFKIkhOKkX/Vjg0R5U/X6IdzZl6lK71KvDbng
 IgEj4hCXkh6ayeMQ2b2g4ywhFIvATkhe7aIj1hpQ6rzJityLQ5kEJMg6+u5hyMaVV5zz
 bMng==
MIME-Version: 1.0
X-Received: by 10.220.92.135 with SMTP id r7mr16435287vcm.11.1397167965179;
 Thu, 10 Apr 2014 15:12:45 -0700 (PDT)
Received: by 10.221.67.136 with HTTP; Thu, 10 Apr 2014 15:12:45 -0700 (PDT)
In-Reply-To: <20140410220411.GB15884@in-addr.com>
References: <CAGHfRMAxbUjiYY5WOtxQLZ=Wzwn25b1sHABwMg0VaCku5sXeRA@mail.gmail.com>
 <20140410220411.GB15884@in-addr.com>
Date: Thu, 10 Apr 2014 15:12:45 -0700
Message-ID: <CAGHfRMCPQU47u5oZ2x1Om_nY9C5EWKvRY2Pr-AbmmiPrHD0H2Q@mail.gmail.com>
Subject: Re: Immutable files on UFS?
From: Garrett Cooper <yaneurabeya@gmail.com>
To: Gary Palmer <gpalmer@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 22:12:46 -0000

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