Re: current syncer bug...

From: Don Lewis <truckman_at_FreeBSD.org>
Date: Mon, 5 Jul 2004 13:06:21 -0700 (PDT)
On  5 Jul, Poul-Henning Kamp wrote:
> 
> Waiting (max 60 seconds) for system process `vnlru' to stop...stopped
> Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped
> Waiting (max 60 seconds) for system process `syncer' to stop...0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Interesting ...

Does it ever print "stopped", or does it hit the 60 second timeout?

Is this a reboot in single user mode when nothing has been written?  If
so, the condition for calling kthread_suspend_check() probably needs to
look for (last_work_seen == -1 && net_worklist_len == 0), and
net_worklist_len needs to be set before this point.

Otherwise, in the following code fragment in sched_sync():

                if (syncer_state != SYNCER_RUNNING && starttime != time_second)
                        printf("%d ", net_worklist_len);

get rid of the (starttime != time_second) condition and add
last_work_seen to the printf().
Received on Mon Jul 05 2004 - 18:06:29 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:00 UTC