Benny Siegert <bsieg...@gmail.com> writes: > Am 06.01.25 um 18:29 schrieb Brad Spencer: >> ci4ic4 <ci4...@proton.me> writes: >>> Weird... >> >> Ya, a bit.. I just tested this on a test box with root user and a >> directory in /var/tmp and was able to add and remove the schg flag and >> was able to remove my testing directory. Are you at some high >> securelevel (sysctl kern.securelevel)?? One of them, forgot which, I >> think restricts the reset of some of the flags. The entire directory >> tree up from the problem directory didn't get the schg flag set on it ...?? > > Could it be filesystem corruption?
Sure... I don't think that fsck will fix something like getting the schg bit set up a directory tree. It would be a very specific mess, but would be the same thing if a corruption changed a directory name. If the filesystem can be recreated without too much trouble, a newfs may be in order. -- Brad Spencer - b...@anduin.eldar.org
