Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Feb 2002 11:11:24 -0800 (PST)
From:      Matthew Dillon <dillon@apollo.backplane.com>
To:        Mike Silbersack <silby@silby.com>
Cc:        Valentin Nechayev <netch@iv.nn.kiev.ua>, "David W. Chapman Jr." <dwcjr@inethouston.net>, <stable@FreeBSD.ORG>
Subject:   Re: cvs commit: src/sys/ufs/ffs ffs_softdep.c
Message-ID:  <200202101911.g1AJBOk30917@apollo.backplane.com>
References:   <20020210113348.P28078-100000@patrocles.silby.com>

next in thread | previous in thread | raw e-mail | index | archive | help

:...
:> directories), but all games used only correct syscall entries and their calls.
:> There was 2 occurences of another variant: __after__ message "Syncing disks...
:> N M\nDone\n", disk activity raised and on 2nd occurence stopped after
:> ~10 seconds, on 1st occurence I wait more than 1 minute for it to terminate
:> and at the end pressed Reset.
:
:Yes, I noticed this problem again as well.  As you say, it only happens if
:there has been significant activity right before the shutdown.  I didn't
:grab a crashdump as I was more worried about what I was testing at the
:time.
:
:Matt, can you reproduce the problem over by you?  It seems that doing
:anything disk intensive and then shutting down immediately will trigger
:it.
:
:Mike "Silby" Silbersack

    Hmm.  I will attempt to reproduce the problem.  How much activity is
    'significant' ?  e.g. equivalent of an rm -rf /usr/ports or something
    smaller?  Do the directories have to be deeply nested for the problem
    to occur?

    On the second issue - long disk activity times after a 'syncing disks...
    done'.  This can occur if there are a lot of dirty VM pages in the
    system belonging to files that need to be written out.  This can take an
    especially long time if a large file was created with ftruncate()
    and written via mmap() instead of write(), because the file can become
    severely fragmented.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202101911.g1AJBOk30917>