Date: Sun, 23 Mar 1997 22:33:52 +0200 (EET) From: Heikki Suonsivu <hsu@clinet.fi> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/3071: 8th sup file flags change randomly Message-ID: <199703232033.WAA07029@katiska.clinet.fi> Resent-Message-ID: <199703232040.MAA27336@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 3071 >Category: kern >Synopsis: File flags change randomly >Confidential: yes >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Mar 23 12:40:01 PST 1997 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.2-RELEASE i386 >Environment: 2.2 from around 8th this month march, kernel compiles around that date, may be supped 1-2 days earlier. Happens on most machines running 2.2 with this late kernel. >Description: I seem to get random flags on files. They change from ls to ls, but the bad thing seems to be that programs or kernel seem to enforce the random flags. This could mean that backups get screwed up and files writable suddenly say they are unwritable or append-only, or files intended to be unmodifiable can be modified. This seems to happen on several machines, almost all of them with the same kernel or from same sup. Earlier kernel from more than a month back seems to work. It happens for files on both NFS and local disks. Curiously, systems with IDE disks do not show this (but it may be due to less load or some other factor). It seems that if machine exhibits this behaviour, it exhibits on all files. The actual flags on disks may be ok, but system behaves like they were random. If the file is local on X and mounted to Y where X shows random flags and Y does not, trying to write to the file in Y results on "operation not permitted" even though flags ls in Y shows "-" for flags. I do not know how long this has been happening, but as nodump also appears there from time to time, this may mean backups silently not dumping lots of files (If dump reads inodes directly, this may not be a problem?). I think I would have noticed if this happened for long time, as the problem is visiable on all files. Reboot does not cure the problem, but I do not quite understand what triggers this. If the files were like this for more than week we would have seen complaints about this and should have noticed it myself. Maybe it just has been there all the time. hsu@news.clinet.fi Sun 12: /bin/ls -l -o /m/katiska/usr/local/etc/sysconfig.kamppi4-gw.helsinki.clinet.fi -rw-r--r-- 1 root bin sappnd 10272 Mar 23 06:00 /m/katiska/usr/local/etc/sysconfig.kamppi4-gw.helsinki.clinet.fi hsu@news.clinet.fi Sun 13: /bin/ls -l -o /m/katiska/usr/local/etc/sysconfig.kamppi4-gw.helsinki.clinet.fi -rw-r--r-- 1 root bin sappnd,schg 10272 Mar 23 06:00 /m/katiska/usr/local/etc/sysconfig.kamppi4-gw.helsinki.clinet.fi hsu@news.clinet.fi Sun 14: /bin/ls -l -o /m/katiska/usr/local/etc/sysconfig.kamppi4-gw.helsinki.clinet.fi -rw-r--r-- 1 root bin sappnd 10272 Mar 23 06:00 /m/katiska/usr/local/etc/sysconfig.kamppi4-gw.helsinki.clinet.fi hsu@news.clinet.fi Sun 15: /bin/ls -l -o /m/katiska/usr/local/etc/sysconfig.kamppi4-gw.helsinki.clinet.fi -rw-r--r-- 1 root bin - 10272 Mar 23 06:00 /m/katiska/usr/local/etc/sysconfig.kamppi4-gw.helsinki.clinet.fi hsu@news.clinet.fi Sun 16: >How-To-Repeat: /bin/ls -l -o (usually this is visible sooner or later). >Fix: Workaround was to revert back to older kernel. Random flags went away. I'll resup tomorrow and see if it was just a bad sup (really weird one). >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703232033.WAA07029>