Subject: bin/29855: dump(8) fails on large filesystems
To: None <gnats-admin@netbsd.org, netbsd-bugs@netbsd.org>
From: None <wojtek@3miasto.net>
List: netbsd-bugs
Date: 04/01/2005 09:59:00
>Number: 29855
>Category: bin
>Synopsis: dump(8) fails on large filesystems
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: bin-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Apr 01 09:59:00 +0000 2005
>Originator: Wojciech Puchar
>Release: 2.0
>Organization:
TENSOR ap
>Environment:
NetBSD chylonia.3miasto.net 2.0 NetBSD 2.0 (chylonia.3miasto.net) #0: Thu Mar 31 23:53:26 CEST 2005 root@chylonia.3miasto.net:/root/chylonia.3miasto.net i386
>Description:
since i change my disk drive from 40 to 160GB (using / filesystem for most of it)
8 partitions:
# size offset fstype [fsize bsize cpg/sgs]
a: 308354671 4225024 4.2BSD 2048 16384 43504 # (Cyl. 4191*- 310098*)
b: 4194304 30720 swap # (Cyl. 30*- 4191*)
c: 312579695 0 unused 0 0 # (Cyl. 0 - 310098*)
d: 312579695 0 unused 0 0 # (Cyl. 0 - 310098*)
e: 30720 0 4.2BSD 1024 8192 15360 # (Cyl. 0 - 30*)
i can't dump(8) it. after about half of the dump i start getting such messages:
piixide0:0: unable to load xfer table DMA map for drive 0, error=22
wd0a: DMA error reading fsbn 7667817788 (wd0 bn 7672042812; cn 7611153 tn 9 sn 21), retrying
piixide0:0: unable to load xfer table DMA map for drive 0, error=22
wd0a: DMA error reading fsbn 7667817788 (wd0 bn 7672042812; cn 7611153 tn 9 sn 21), retrying
piixide0:0: unable to load xfer table DMA map for drive 0, error=22
wd0a: DMA error reading fsbn 7667817788 (wd0 bn 7672042812; cn 7611153 tn 9 sn 21), retrying
piixide0:0: unable to load xfer table DMA map for drive 0, error=22
wd0a: DMA error reading fsbn 7667817788 (wd0 bn 7672042812; cn 7611153 tn 9 sn 21), retrying
wd0a: error reading fsbn 7667817788 (wd0 bn 7672042812; cn 7611153 tn 9 sn 21), retrying
wd0: (id not found)
wd0a: error reading fsbn 7667817788 (wd0 bn 7672042812; cn 7611153 tn 9 sn 21)wd0: (id not found)
sector number is pure nonsense here (it's far too high). and dump doesn't work of course.
it worked well with 40GB drive
>How-To-Repeat:
try to dump big >100GB (i think) filesystem
>Fix:
no idea