From owner-freebsd-current Wed Nov 21 14:49:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp016.mail.yahoo.com (smtp016.mail.yahoo.com [216.136.174.113]) by hub.freebsd.org (Postfix) with SMTP id BD15437B41A for ; Wed, 21 Nov 2001 14:49:09 -0800 (PST) Received: from mkc-65-30-96-67.kc.rr.com (HELO yahoo.com) (65.30.96.67) by smtp.mail.vip.sc5.yahoo.com with SMTP; 21 Nov 2001 22:49:09 -0000 Message-ID: <3BFC2153.2090508@yahoo.com> Date: Wed, 21 Nov 2001 15:49:07 -0600 From: Jim Bryant Reply-To: kc5vdj@yahoo.com User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: "David W. Chapman Jr." Cc: Mikhail Teterin , current@freebsd.org Subject: Re: damaged file system despite unmounts References: <200111211417.fALEHEO60866@aldan.algebra.com> <20011121153518.GB91521@leviathan.inethouston.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I recently [this week] had to revert to a tape backup of an out-of-sync /var because yet again, /var got mangled on 'shutdown -r now', this time, and I reported this to the list the first time this happened, is the second time I have had to do this, so this seems to be an ongoing issue. I have also receieved a lot of master superblock bad notices and had to manually fix those in between the two occurrances [the first was several months ago], anyhow, just like the first time, I got the master superblock bad warning, as well as the invalid label message. For some reason this always happens with /var, yet with no other filesystem. This time I newfs'ed without softupdates. We'll see what happens. David W. Chapman Jr. wrote: > On Wed, Nov 21, 2001 at 09:17:13AM -0500, Mikhail Teterin wrote: > >>For a while I was noticing my largest FS reported as not unmounted >>cleanly on boot. Today I decided to unmount it myself and check it with >>fsck. Here are the results. Notice, that the first fsck had to mark the >>FS clean. Notice that the second fsck found something else to do, and >>only the third one was happy. What's happening? Thanks, >> >> -mi >> >> > I noticed this a while ago on -current. I haven't checked recently, > but I do remember having this problem > > jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! ----------------------------------------------------- POWER TO THE PEOPLE! ----------------------------------------------------- "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message