NetBSD Problem Report #6916

Received: (qmail 24839 invoked from network); 31 Jan 1999 04:13:31 -0000
Message-Id: <199901310412.WAA01386@warthog.com>
Date: Sat, 30 Jan 1999 22:12:18 -0600 (CST)
From: windsor@warthog.com
Reply-To: windsor@warthog.com
To: gnats-bugs@gnats.netbsd.org
Subject: narcoleptic dump(8)
X-Send-Pr-Version: 3.95

>Number:         6916
>Category:       kern
>Synopsis:       My dump/restore went to sleep!
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    lukem
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jan 30 20:20:01 +0000 1999
>Closed-Date:    Sun Mar 16 03:24:06 +0000 2003
>Last-Modified:  Sun Mar 16 03:24:06 +0000 2003
>Originator:     Rob Windsor
>Release:        1.3.3
>Organization:
NosePickers Anonymous
>Environment:
System: NetBSD evolution 1.3.3 NetBSD 1.3.3 (EVOLUTION) #5: Sat Jan 23 01:00:29 CST 1999 windsor@evolution:/usr/src/sys/arch/sparc/compile/EVOLUTION sparc


>Description:
	I was doing a "dump | restore" action from cron (one disk to another)
	and dump went to la-la land.  The crontab has the following lines
	(just so that you understand what is happening):

		mount /dev/sd1d /mirror/work
		(cd /mirror/work ; dump 0f - /usr | restore -rf - )

	Top shows:

  PID USERNAME PRI NICE   SIZE   RES STATE   TIME   WCPU    CPU COMMAND
  758 windsor   28    0   972K  120K run     7:25  0.93%  0.93% top
  513 root       2    0   788K   68K sleep   1:36  0.05%  0.05% sshd1
  855 root       2    0  4196K   48K sleep   2:39  0.00%  0.00% restore
  159 root      18    0    20K    8K sleep   0:56  0.00%  0.00% update
  857 root      18   -5   600K   32K sleep   0:29  0.00%  0.00% dump
  859 root      18   -5   600K   32K sleep   0:28  0.00%  0.00% dump
  858 root      18   -5   600K   32K sleep   0:28  0.00%  0.00% dump
  205 root       2    0   368K  108K sleep   0:20  0.00%  0.00% sshd1
  487 root       2    0   788K   84K sleep   0:15  0.00%  0.00% sshd1
  856 root       2   -5   656K   88K sleep   0:12  0.00%  0.00% dump
   97 root      10    0    36K    8K sleep   0:11  0.00%  0.00% ipmon
  125 root      10    0    64M    0K sleep   0:11  0.00%  0.00% mount_mfs
  755 windsor    2    0   108K   20K sleep   0:10  0.00%  0.00% tail
  462 root       2    0   788K   68K sleep   0:07  0.00%  0.00% <sshd1>
  854 root      10   -5   600K   76K sleep   0:03  0.00%  0.00% <dump>

	(after it wedged, I tried to renice the dump processes to wake
	them up)

ps -alx shows:

: evolution; ps alx | egrep 'dump|restore|PPID'
  UID   PID  PPID CPU PRI NI   VSZ  RSS WCHAN  STAT TT       TIME COMMAND
    0   854   853  93  10 -5   600   76 wait   IW<  ??    0:03.55 dump 0f - /us
    0   855   853 170   2  0  4196   48 netio  I    ??    2:39.19 (restore)
    0   856   854  15   2 -5   656   88 netio  I<   ??    0:12.62 dump 0f - /us
    0   857   856  25  18 -5   600   32 pause  I<   ??    0:29.05 dump 0f - /us
    0   858   856  28  18 -5   600   32 pause  I<   ??    0:28.65 dump 0f - /us
    0   859   856  25  18 -5   600   32 pause  I<   ??    0:28.42 dump 0f - /us
  101  1248   489   8  30  0    84   84 -      R+   p1    0:00.08 egrep dump|re


>How-To-Repeat:
	hmm.  do a "dump | restore" from one disk to another with enough
	stuff going on that one of the dump processes page out?  I'm not
	sure how this happened, so I'm not sure how to repeat it.

>Fix:
	nfc

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: thorpej 
State-Changed-When: Wed Aug 4 22:38:15 PDT 1999 
State-Changed-Why:  
This may have been due to a compiler bug.  Is it still a problem 
for you in recent current (with a very up-to-date gcc)? 

From: Rob Windsor <windsor@warthog.com>
To: thorpej@netbsd.org
Cc: kern-bug-people@netbsd.org
Subject: Re: kern/6916 
Date: Mon, 09 Aug 1999 08:06:41 -0500

 Verily did thorpej@netbsd.org write:

 > Synopsis: My dump/restore went to sleep!
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: thorpej
 > State-Changed-When: Wed Aug 4 22:38:15 PDT 1999
 > State-Changed-Why: 
 > This may have been due to a compiler bug.  Is it still a problem
 > for you in recent current (with a very up-to-date gcc)?

 I'll check this week.

 (How do I add my reply to gnats?)

 -- Rob
 ----------------------------------------
 Internet: windsor@warthog.com                             __o
 Life: Rob@Carrollton.Texas.USA.Earth                    _`\<,_
                                                        (_)/ (_)
 The weather is here, wish you were beautiful.

State-Changed-From-To: feedback->closed 
State-Changed-By: hwr 
State-Changed-When: Wed Sep 1 12:25:28 PDT 1999 
State-Changed-Why:  
Closed on request of submitter. Seems to work from 1.4J on 
State-Changed-From-To: closed->open 
State-Changed-By: windsor 
State-Changed-When: Fri Oct 22 14:39:56 PDT 1999 
State-Changed-Why:  
problem still exists afterall 
State-Changed-From-To: open->feedback 
State-Changed-By: lukem 
State-Changed-When: Sun Dec 23 08:11:32 PST 2001 
State-Changed-Why:  
Can  you try a -current dump(8) ? 
I've fixed a couple of "dump appears to hang doing SFA" type bugs that 
crept in in early 1998 that you might have hit when you hit this the 
second time after thorpej thought it might have been fixed by a compiler 
upgrade 


Responsible-Changed-From-To: kern-bug-people->lukem 
Responsible-Changed-By: lukem 
Responsible-Changed-When: Sun Dec 23 08:11:32 PST 2001 
Responsible-Changed-Why:  
State-Changed-From-To: feedback->closed 
State-Changed-By: lukem 
State-Changed-When: Sat Mar 15 19:23:19 PST 2003 
State-Changed-Why:  

I'm pretty sure that the problem Rob was having has been fixed. 
If you experience any problems like this in -current's dump (from 2003/03/16 
or newer), please open a new PR 

>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.