Bug 16812

Summary:	level 0 dump runs forever -- generates a backup much larger than the available disk.
Product:	Base System	Reporter:	dlacroix <dlacroix>
Component:	bin	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me	CC:	dlacroix
Priority:	Normal
Version:	3.4-STABLE
Hardware:	Any
OS:	Any

Description dlacroix 2000-02-18 21:30:00 UTC

any level 0 dump continuously runs, generating a backup that is 
far larger than the entire disk that's being backed up.

# dump 0f - /usr >/dev/null                              [2:24PM]
  DUMP: Date of this level 0 dump: Fri Feb 18 14:24:51 2000
  DUMP: Date of last level 0 dump: the epoch
  DUMP: Dumping /dev/rwd0s2f (/usr) to standard output
  DUMP: mapping (Pass I) [regular files]
  DUMP: mapping (Pass II) [directories]
  DUMP: estimated 3026622 tape blocks.
  DUMP: dumping (Pass III) [directories]
  DUMP: dumping (Pass IV) [regular files]
  DUMP: 3.10% done, finished in 2:36
  DUMP: 30.04% done, finished in 0:23
  DUMP: 103.97% done, finished in 0:00
  DUMP: 180.31% done, finished in 0:-8
  DUMP: 257.37% done, finished in 0:-15
  DUMP: 332.97% done, finished in 0:-20
^C  DUMP: Interrupt received.

This behavior was noticed first when Amanda did a level 0 backup on
monday night.  Amanda had a 300Gb backup size for the /usr partition
on this computer.   

Factors that my have contributed to this?
- Power outage monday morning, caused machine to go down, and
it required a manual fsck before it would boot up again.
- I unpacked a NetBSD 1.4.1 for macPPC on /usr/export in while
attempting to get a Powermac to netboot.

I searched through and deleted the NetBSD export directory, but 
found nothing but normal files, directories, and symbolic links,
tried deleting the entire directory, and dump still exhibits the
same behavior.

I have also shut down the machine, forced an FSCK on the partition
before it was mounted, attempted the same dump (again redirected to 
/dev/null), and it STILL exhibited the same behavior.

If there were some way to run some verbose UFS analyzer, or some
debugging flags to dump that I could try, I'll gladly send that
output to someone who could help.

I am really not comfortable with the idea of not being able to 
backup this partition properly, I need this to be backed up regularly.

How-To-Repeat: 
I'm wishing I knew what was causing this, I suspect the power outage 
damaged my disk integrity in such a way that it tickles something in
dump, but it's some inconsistency that's not recognized by fsck, and
I haven't the foggiest idea how to correct it.

Comment 1 Poul-Henning Kamp freebsd_committer

2001-06-06 21:53:44 UTC

State Changed
From-To: open->closed

Sounds like you need a full FSCK and a find to locate sparse files.