deadlock or bad disk ? RELENG_8
Jeremy Chadwick
freebsd at jdc.parodius.com
Sun Jul 18 21:14:18 UTC 2010
On Sun, Jul 18, 2010 at 05:08:09PM -0400, Mike Tancsa wrote:
>
>
> On the serial console I see
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 74, size: 4096
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 128, size: 20480
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 69, size: 4096
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 6, size: 4096
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 74, size: 4096
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 128, size: 20480
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 69, size: 4096
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 6, size: 4096
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 74, size: 4096
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 128, size: 20480
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 69, size: 4096
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 6, size: 4096
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 74, size: 4096
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 128, size: 20480
> [...]
> load: 0.00 cmd: csh 73167 [vnread] 22.32r 0.00u 0.00s 0% 3232k
> load: 0.00 cmd: csh 73167 [vnread] 22.65r 0.00u 0.00s 0% 3232k
> load: 0.00 cmd: csh 73167 [vnread] 22.96r 0.00u 0.00s 0% 3232k
> load: 0.00 cmd: csh 73167 [vnread] 23.20r 0.00u 0.00s 0% 3232k
> load: 0.00 cmd: csh 73167 [vnread] 23.40r 0.00u 0.00s 0% 3232k
> load: 0.00 cmd: csh 73167 [vnread] 23.61r 0.00u 0.00s 0% 3232k
Where exactly is your swap partition? I ask because of the below
paragraph starting with "Its RELENG_8 amd64 from July 13th ...".
> Its RELENG_8 amd64 from July 13th and the swap is on an ARECA drive
> and I dont see any errors on any of the raidset members. I also have
> a large zfs spool and a small mount point on a 3ware controller but
> unfortunately, nothing in the logs post reboot and nothing from
> smartctl
If you Google for "swap_pager: indefinite wait buffer: bufobj" you'll
find this is a pretty well-established problem, but the situation varies
per person. A common one is here (read the entire thread):
http://www.mail-archive.com/freebsd-questions@freebsd.org/msg192481.html
I have no advice as far as how to solve this problem.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
More information about the freebsd-stable
mailing list