From owner-freebsd-bugs Sat Apr 12 11:30:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA14762 for bugs-outgoing; Sat, 12 Apr 1997 11:30:05 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA14755; Sat, 12 Apr 1997 11:30:03 -0700 (PDT) Resent-Date: Sat, 12 Apr 1997 11:30:03 -0700 (PDT) Resent-Message-Id: <199704121830.LAA14755@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, sigma@pair.com Received: from upsilon.pair.com (upsilon.pair.com [207.86.128.35]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA14655 for ; Sat, 12 Apr 1997 11:27:43 -0700 (PDT) Received: (from root@localhost) by upsilon.pair.com (8.8.5/8.6.12) id OAA10583; Sat, 12 Apr 1997 14:27:37 -0400 (EDT) Message-Id: <199704121827.OAA10583@upsilon.pair.com> Date: Sat, 12 Apr 1997 14:27:37 -0400 (EDT) From: sigma@pair.com Reply-To: sigma@pair.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3267: mtime/ctime sometimes updated when a program is run Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3267 >Category: kern >Synopsis: mtime/ctime sometimes updated when a program is run >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 12 11:30:01 PDT 1997 >Last-Modified: >Originator: Kevin Martin >Organization: pair Networks >Release: FreeBSD 2.2.1-RELEASE i386 >Environment: Fresh 2.2.1-RELEASE installation, no active users, only cron jobs. >Description: Cron jobs, which run every ten minutes, make several calls to /usr/bin/grep and /usr/bin/wc - once or twice per day, these files get their ctime and mtime updated to the current time. This has also been seen in the past with 2.2-BETA_A and 2.2-GAMMA. It has been reported as early as February 1996 for FreeBSD 2.0.5. The most serious concern is that when this problem was occuring on a heavily loaded 2.2-BETA_A system, we also saw numerous filesystem corruptions (disappearing files, etc) - although there is no proof that this is related. >How-To-Repeat: Have been unable to repeat by running programs manually many times, but it happens routinely if not consistently when run from a cron job (as root). See also the archives of freebsd-bugs and freebsd-questions, when searched for "mtime and ctime". >Fix: Unknown. Errant filesystem bug? >Audit-Trail: >Unformatted: