misc/181565: Problem with vnode-backed swap space.

Eddy Beaupre eddy at beaupre.biz
Mon Aug 26 15:00:00 UTC 2013


>Number:         181565
>Category:       misc
>Synopsis:       Problem with vnode-backed swap space.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Aug 26 15:00:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Eddy Beaupre
>Release:        10.0-CURRENT (r254904)
>Organization:
>Environment:
FreeBSD vfs.beaupre.biz 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r254904: Mon Aug 26 09:09:58 EDT 2013     root at vfs.beaupre.biz:/usr/obj/usr/src/sys/LOVEVPS  amd64
>Description:
Vnode-backed swap space doesn't seem to work at boot. md0 is created but the swap memory is not added to the system and swapon complain that it is already in use.

Manually releasing md0 (mdconfig -d -u0) and running swapon -a fix the problem but must be done at every boot.

My fstab entry for the swapfile is the following:

md   none   swap   sw,file=/var/spool/swap/swapfile   0   0


>How-To-Repeat:
1) Add a swafile via /etc/fstab:
md   none   swap   sw,file=/var/spool/swap/swapfile   0   0

2) reboot the system and check if the swapfile is avalable.


>Fix:
More a workaround, once boot do the following as root:

# mdconfig -d -u0
# swapon -a





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


More information about the freebsd-bugs mailing list