From owner-freebsd-fs Mon Jul 15 10:36:23 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EE6837B729; Mon, 15 Jul 2002 10:35:51 -0700 (PDT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD2E444245; Mon, 15 Jul 2002 10:21:57 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 5F73AAE03F; Mon, 15 Jul 2002 10:20:55 -0700 (PDT) Date: Mon, 15 Jul 2002 10:20:55 -0700 From: Alfred Perlstein To: fs@freebsd.org Cc: bde@freebsd.org, mckusick@freesd.org Subject: (forw) atime patch tested and fixed for 4.6 (fwd) Message-ID: <20020715172055.GM77219@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org A friend whipped this patch up, what it does is update atime when mtime/ctime change. Is this ok? ----- Forwarded message from Nick Johnson ----- From: Nick Johnson To: Subject: atime patch tested and fixed for 4.6 (fwd) Date: Mon, 15 Jul 2002 00:12:21 -0700 (PDT) Message-ID: ---------- Forwarded message ---------- Date: Mon, 8 Jul 2002 19:50:25 -0700 (PDT) From: Nick Johnson To: alfred@freebsd.org Subject: atime patch tested and fixed for 4.6 [turing] ~/atime> perl testpatch.pl file created; atime=1026182996, mtime=1026182996, ctime=1026182996 file read; atime=1026182997, mtime=1026182996, ctime=1026182996 file append; atime=1026182998, mtime=1026182998, ctime=1026182998 [turing] ~/atime> su Password: turing# mount -o noatime -u /home turing# exit [turing] ~/atime> perl testpatch.pl file created; atime=1026183032, mtime=1026183032, ctime=1026183032 file read; atime=1026183032, mtime=1026183032, ctime=1026183032 file append; atime=1026183034, mtime=1026183034, ctime=1026183034 [turing] ~/atime> and here's the patch: --- ufs_vnops.c.orig Tue Feb 5 10:35:04 2002 +++ ufs_vnops.c Mon Jul 8 19:07:48 2002 @@ -159,6 +159,18 @@ ip->i_flag |= IN_LAZYMOD; else ip->i_flag |= IN_MODIFIED; + /* + * If we're going to be updating or changing, + * it makes sense that we're accessing as well. + * This changes the traditional semantics of + * mount -o noatime slightly. + */ + if (!(ip->i_flag & IN_ACCESS) && + ((ip->i_flag & IN_UPDATE) || + (ip->i_flag & IN_CHANGE))) { + ip->i_flag |= IN_ACCESS; + } + if ((vp->v_mount->mnt_flag & MNT_RDONLY) == 0) { vfs_timestamp(&ts); if (ip->i_flag & IN_ACCESS) { Nick -- "The aptly-named morons.org is an obscenity-laced screed..." -- Robert P. Lockwood, Catholic League director of research Nick Johnson, version 2.0 http://www.spatula.net/ ----- End forwarded message ----- -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Jul 15 13: 4: 2 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BA2B37B400; Mon, 15 Jul 2002 13:04:00 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B0A343E3B; Mon, 15 Jul 2002 13:03:59 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id GAA01702; Tue, 16 Jul 2002 06:03:55 +1000 Date: Tue, 16 Jul 2002 06:07:26 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Alfred Perlstein Cc: fs@freebsd.org, , Subject: Re: (forw) atime patch tested and fixed for 4.6 (fwd) In-Reply-To: <20020715172055.GM77219@elvis.mu.org> Message-ID: <20020716055722.Q41780-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 15 Jul 2002, Alfred Perlstein wrote: > A friend whipped this patch up, what it does is update atime when > mtime/ctime change. Is this ok? I disklike it for the same reasons as when it was proposed before. > and here's the patch: > > --- ufs_vnops.c.orig Tue Feb 5 10:35:04 2002 > +++ ufs_vnops.c Mon Jul 8 19:07:48 2002 > @@ -159,6 +159,18 @@ > ip->i_flag |= IN_LAZYMOD; > else > ip->i_flag |= IN_MODIFIED; > + /* > + * If we're going to be updating or changing, > + * it makes sense that we're accessing as well. > + * This changes the traditional semantics of > + * mount -o noatime slightly. > + */ > + if (!(ip->i_flag & IN_ACCESS) && > + ((ip->i_flag & IN_UPDATE) || > + (ip->i_flag & IN_CHANGE))) { > + ip->i_flag |= IN_ACCESS; > + } > + > if ((vp->v_mount->mnt_flag & MNT_RDONLY) == 0) { > vfs_timestamp(&ts); > if (ip->i_flag & IN_ACCESS) { > A better way would be to set IN_ACCESS without checking MNT_NOATIME elsewhere, and either ignore it or unset it here if MNT_NOATIME is set and one of the other IN_* flags is not set. It doesn't make sense that we are accessing if we didn't set the access flag. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Jul 18 8:57:29 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A86F837B400 for ; Thu, 18 Jul 2002 08:57:20 -0700 (PDT) Received: from agena.meridian-enviro.com (thunder.meridian-enviro.com [207.109.234.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id E537843E6D for ; Thu, 18 Jul 2002 08:57:10 -0700 (PDT) (envelope-from rand@meridian-enviro.com) Received: from delta.meridian-enviro.com (delta.meridian-enviro.com [10.10.10.43]) by agena.meridian-enviro.com (8.11.6/8.11.6) with ESMTP id g6IFv5l56446 for ; Thu, 18 Jul 2002 10:57:05 -0500 (CDT) (envelope-from rand@meridian-enviro.com) Date: Thu, 18 Jul 2002 10:57:05 -0500 Message-ID: <87y9c9hvvy.wl@delta.meridian-enviro.com> From: "Douglas K. Rand" To: freebsd-fs@freebsd.org Subject: Unexpected FS rot. User-Agent: Wanderlust/2.9.7 (Unchained Melody) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.4 (patch 8) (Honest Recruiter) (i386--freebsd) X-Face: $L%T~#'9fAQ])o]A][d7EH`V;"_;2K;TEPQB=v]rDf_2s% List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The other day we had a mildly embarrassing event when we closed up a case on one of our dual Athlon systems with out turning the case fans on first. (There is this helpful switch to allow you to "hot swap" the fans.) So the Athlon's essentially turned themselves off after getting too hot, which froze the system. After figuring out what we did wrong (lots of Duh! going around that afternoon) we brought the system back up. As is our habit, we came up into single-user mode and did a fsck by hand, and had only one file system (/project/Vault) with any serious problems. The filesystem had 167 INCORRECT BLOCK COUNT errors in phase 1, 590 UNREF FILE errors and 13 LINK COUNT DIR errors in phase 2, and 34 ALLOCATED FRAG [number] MARKED FREE errors in phase 5, along with the usual FREE BLK COUNT(S) WRONG IN SUPERBLK, SUMMARY INFORMATION BAD, and BLK(S) MISSING IN BIT MAPS. Certainly one of the dirtier filesystems that I've had to repair. And since I've had problems before with a single fsck not catching everything, I ran fsck again on all the filesytems, and this file system checked clean the second time. [On an (I think) unrelated note, the /usr file system didn't check clean the second time, it complained about FREE BLK COUNT(S) WRONG IN SUPERBLK, SUMMARY INFORMATION BAD, and ALLOCATED INODE 2103 MARKED FREE - BLK(S) MISSING IN BIT MAPS. A third fsck reported clean.] So we brought the system up and started using it. A day later we noticed a few of these problems: $ ls -l /project/Vault/tmp/raw/blobs/nids/27.3/7d27120e 0104.1d8bf700: Bad file descriptor 0702.2495bce8: Bad file descriptor 0c39.38a05298: Bad file descriptor total 154 -rw-r--r-- 1 weather wx 12538 Jul 18 09:19 122a.2dc7e110 -rw-r--r-- 1 weather wx 12480 Jul 18 09:25 1901.253e6c80 -rw-r--r-- 1 weather wx 12478 Jul 18 09:31 1e39.2198ad70 -rw-r--r-- 1 weather wx 12312 Jul 18 09:36 240e.16a25f60 -rw-r--r-- 1 weather wx 12468 Jul 18 09:42 2a0f.02dbe348 -rw-r--r-- 1 weather wx 12636 Jul 18 09:50 3016.2d588d10 -rw-r--r-- 1 weather wx 12622 Jul 18 09:54 3604.19f22e70 -rw-r--r-- 1 weather wx 12456 Jul 18 09:59 3b21.22af6500 Which didn't seem good at all. We made /project/Vault quiet, umounted it, and fsck'ed it, and lo and behold there were problems: It reported UNEXPECTED SOFT UPDATE INCONSISTENCY, and asked us to remove those files that reported a bad file descriptor. Everything has been working just fine since then, but what has me somewhat befuddled is that we had a clean fsck, and then the file system just started to rot. This is a 4.5-RELEASE-p8 system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Jul 18 9:43:50 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43A5137B401 for ; Thu, 18 Jul 2002 09:43:48 -0700 (PDT) Received: from bilver.wjv.com (user38.net339.fl.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4EDD43E67 for ; Thu, 18 Jul 2002 09:43:45 -0700 (PDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.11.6/8.11.6) id g6IGhTP52300; Thu, 18 Jul 2002 12:43:29 -0400 (EDT) (envelope-from bv) Date: Thu, 18 Jul 2002 12:43:29 -0400 From: Bill Vermillion To: "Douglas K. Rand" Cc: freebsd-fs@FreeBSD.ORG Subject: Re: Unexpected FS rot. Message-ID: <20020718164329.GB52076@wjv.com> Reply-To: bv@wjv.com References: <87y9c9hvvy.wl@delta.meridian-enviro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87y9c9hvvy.wl@delta.meridian-enviro.com> User-Agent: Mutt/1.3.25i Organization: W.J.Vermillion / Orlando - Winter Park Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Douglas K. Rand, the prominent pundit, on Thu, Jul 18, 2002 at 10:57 while half mumbling, half-witicized: > The other day we had a mildly embarrassing event when we closed up a > case on one of our dual Athlon systems with out turning the case fans > on first. (There is this helpful switch to allow you to "hot swap" the > fans.) > So the Athlon's essentially turned themselves off after getting too > hot, which froze the system. After figuring out what we did wrong > (lots of Duh! going around that afternoon) we brought the system back > up. That's one reason that many advise not using Athon's in critical server systems. The P4 equivalents will throttle back their clock speed so as not to overheat. tomshardware.com had some pretty graphic pictures of Athlons that had melted - in under one second - when the CPU fans died. Later chip sets detect Athlon overheating and just shut the system down. ... Bill -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Jul 19 20:22:55 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8129B37B400; Fri, 19 Jul 2002 20:22:47 -0700 (PDT) Received: from everyday.com (host66-233.pool217141.interbusiness.it [217.141.233.66]) by mx1.FreeBSD.org (Postfix) with SMTP id E9DEE43E3B; Fri, 19 Jul 2002 20:22:38 -0700 (PDT) (envelope-from alisia_morelli@everyday.com) Received: from 66.119.111.151 ([66.119.111.151]) by asy100.as122.sol.superonline.com with smtp; Sat, 20 Jul 2002 02:35:49 +0100 Received: from [71.251.195.73] by mta05bw.bigpond.com with local; 20 Jul 2002 12:35:09 -0900 Received: from smtp-server6.tampabay.rr.com ([44.6.38.78]) by smtp013.mail.yahoo.com with local; 20 Jul 2002 03:34:29 -0000 Received: from anther.webhostingtalk.com ([153.167.34.13]) by smtp4.cyberec.com with local; 19 Jul 2002 20:33:49 +0700 Reply-To: Message-ID: <025b88d87d4d$7332e5e7$0ea71de1@onxsat> From: To: Member@FreeBSD.ORG Subject: domain names now only $14.95 Date: Sat, 20 Jul 2002 11:25:24 -0800 MiME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: The Bat! (v1.52f) Business Importance: Normal Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org PUBLIC ANNOUNCEMENT: The new domain names are finally available to the general public at discount prices. Now you can register one of the exciting new .BIZ or .INFO domain names, as well as the original .COM and .NET names for just $14.95. These brand new domain extensions were recently approved by ICANN and have the same rights as the original .COM and .NET domain names. The biggest benefit is of-course that the .BIZ and .INFO domain names are currently more available. i.e. it will be much easier to register an attractive and easy-to-remember domain name for the same price. Visit: http://www.affordable-domains.com today for more info. Register your domain name today for just $14.95 at: http://www.affordable-domains.com/ Registration fees include full access to an easy-to-use control panel to manage your domain name in the future. Sincerely, Domain Administrator Affordable Domains To remove your email address from further promotional mailings from this company, click here: http://www.centralremovalservice.com/cgi-bin/domain-remove.cgi 8275HiSK2-398l12 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message