amd64/138709: [patch] FreeBSD/amd64 can't see all system memory

[James R. Van Artsdalen]

>Number:         138709
>Category:       amd64
>Synopsis:       [patch] FreeBSD/amd64 can't see all system memory
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Sep 10 18:20:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     James R. Van Artsdalen
>Release:        FreeBSD 9.0-CURRENT amd64
>Organization:
>Environment:
System: FreeBSD pygmy.housenet.jrv 9.0-CURRENT FreeBSD 9.0-CURRENT #4 r197044M: Wed Sep  9 18:58:08 CDT 2009     james at pygmy.housenet.jrv:/usr/obj/usr/src/sys/GENERIC  amd64


>Description:

ZFS recv hung last night during the daily periodic script.  Most of the
pool can be read but if one area is touched the process hangs with ^T
reporting:

$ find /bigtex
...
/bigtex/usr/home/james
^T
load: 0.00  cmd: find 2794 [rrl->rr_cv)] 5861.45r 0.28u 2.02s 0% 1704k

That's about where the ZFS recv hung:

receiving incremental stream of
bigtex/usr/home/james/News at syssnap-1246856401 into bigtex/usr/home/james/News at syssnap-1246856401
received 15.8MB stream in 59 seconds (275KB/sec)
receiving incremental stream of
bigtex/usr/home/james/News at syssnap-1246942803 into bigtex/usr/home/james/News at syssnap-1246942803
received 5.91MB stream in 50 seconds (121KB/sec)
receiving incremental stream of
bigtex/usr/home/james/News at syssnap-1247029203 into bigtex/usr/home/james/News at syssnap-1247029203

There should have 25 or so more snapshots in that filesystem.

/var/log/messages has no messages.

The replication stream has many filesystem deletes and renames.



>How-To-Repeat:
repeatabioity not yet clear.

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: