[DragonFlyBSD - Bug #1937] (Closed) vnconfig and swapfile

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Thu Aug 20 09:05:53 PDT 2015

Issue #1937 has been updated by swildner.

Description updated
Status changed from New to Closed

Setting up a swapfile just via vnconfig(8) does in fact work here (4.3 master), therefore I'm closing the issue.

advancer# truncate -s700M swap
advancer# vnconfig -e vn0 swap swap
advancer# swapinfo -k
Device          1K-blocks     Used    Avail Capacity  Type
/dev/da0s1b      67108864       32 67108832     0%    Interleaved
/dev/vn0           716800        0   716800     0%    Interleaved
Total            67825664       32 67825632     0%

It can also be configured via rc.conf:


I don't know what was wrong at the time this bug was filed.

Bug #1937: vnconfig and swapfile

* Author: nonsolosoft
* Status: Closed
* Priority: Normal
* Assignee: thomas.nikolajsen
* Category: 
* Target version: 

probably there is something wrong or obsolete in:

lap# truncate -s700M /dati/swapfile
lap# chmod 0600 /dati/swapfile
lap# vnconfig -e vn0 /dati/swapfile swap
vnconfig: swapon: Device not configured
lap# vnconfig -l
vn0: covering /dati/swapfile on ad0s2h, inode 409
vn1: not in use
vn2: not in use
vn3: not in use
lap# ls /dev/vn*
/dev/vn         /dev/vn0s0      /dev/vn2
/dev/vn0        /dev/vn1        /dev/vn3
lap# swapon /dev/vn0
swapon: /dev/vn0: Device not configured
lap# swapon /dev/vn0s0
swapon: /dev/vn0s0: Device not configured

Best wishes,             \ferz

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list