[Bug 181565] [swap] Problem with vnode-backed swap space.

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181565

elij <elij+***@wundrd.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |elij+***@wundrd.net

--- Comment #2 from elij <elij+***@wundrd.net> ---
Having the same problem.

This worked on 10.0-RELEASE. After upgrading to 10.1-RELEASE, it no longer
works.

/etc/fstab:
md99 none swap sw,file=/swap0 0 0

After boot:
# mdconfig -lv
md99 vnode 256M /swap0

# swapinfo
Device 1K-blocks Used Avail Capacity
#


Deleting the md and calling swapon by hand works.

# mdconfig -d -u 99; swapon -a; swapinfo -h
swapon: adding /dev/md99 as swap device
Device 1K-blocks Used Avail Capacity
/dev/md99 262144 0B 256M 0%

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181565

Robert Schulze <***@bytecamp.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@bytecamp.net

--- Comment #3 from Robert Schulze <***@bytecamp.net> ---
If you add "late" to the mount options, it will work. This is not properly
documented.

With kind regards,
Robert Schulze

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181565

Mark Millard <***@dsl-only.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@dsl-only.net

--- Comment #4 from Mark Millard <***@dsl-only.net> ---
FYI: See

Bug 206048 - 11.0-CURRENT -r293227 (and others) arm (rpi2/BeagleBone Black)
amd64 etc: swapfile usage hangs; swap partition works

for a problem that may apply to 10.x as well when using things like:

file=/var/spool/swap/swapfile
file=/swap0

--unless those files are on their own file systems/partitions not used for
other (used) files. (A swap file by itself on its own partition/file system has
not shown the problem. Mixing with other IO from the same file system/partition
does. But only so much information can be put in a subject line.)

It may be worth testing if the involved 10.x context(s) hang before settling on
this sort of placement of the file. One of the comments suggested a command
like:

stress -d 2 -m 3 --vm-keep

was sufficient to show the problem on at least 11.0-CURRENT amd64 contexts. I
guess that command is from the port sysutils/stress .

It would actually be good to have 10.x comments in Bug 206048 reporting how
such testing went if someone tries it.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181565

Eitan Adler <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #5 from Eitan Adler <***@FreeBSD.org> ---
*** Bug 204485 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181565

Mark Linimon <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@FreeBSD.org
See Also| |https://bugs.freebsd.org/bu
| |gzilla/show_bug.cgi?id=2060
| |48

--- Comment #6 from Mark Linimon <***@FreeBSD.org> ---
^To submitter: is this still a problem on supported versions of FreeBSD?

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181565

--- Comment #7 from Mark Millard <marklmi26-***@yahoo.com> ---
(In reply to Mark Linimon from comment #6)

See:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206048#c10

and Comment #4 here for more fundamental, overall problem for
vnode-backed swap space.

Things trace back to the quote of what kib reported on a
list, see:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206048#c7