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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
