Moinak Ghosh wrote:
Ian Murdock wrote:
Tim Foster wrote:
[...]
Partly, ZFS isn't yet supported as a dump device, and while you can swap
to a zvol, I believe there's plans to change the way swap to ZFS works
so we're not going through the zvol layer. For now, allocating a normal
swap device would be a really sane thing to do (we *definitely* need to
be able to savecore(1M) for Indiana!!)
Agreed. (Also note that this is a feature that Linux has never
supported out of the box, though there's certainly been demand for it.
In fact, kernel debugging support in Linux has always been
terrible. Another competitive differentiator, for those keeping track.)
Rather than worrying about creating a slice just for swap, can we reuse
the Linux swap partition if one already exists, or use a full partition
for swap if not? I know Moinak/Belenix has done some work here, and
it looks like it works too (though it's labeled "experimental" in 0.6).
It works but does not support it being configured as a dump device.
lofi(7D)
is used to make a segment of the disk appear as a pseudo block device
in case
of an extended partition. Using lofi allows preventing access to the
beginning
of the Linux swap partition to avoid overwriting the initial page of
data that
defines the swap characteristics. Linux complains if this is
clobbered. Lofi
however does not support dumping to it.
This is kludgy but allows a LiveCD to get some more swap space. The
proper solution is to get full extended partition support and there is a
project underway to get that. Once that is available a simple swap -a
<swaplow> <swaplen> can be used to avoid overwriting the initial page
of the Linux swap in all cases (primary and extended).
If we can't make "swap -a <device>" work then we're not doing it right.
Nobody should ever be asked to get numbers like swaplow and swaplen right.
Dave
_______________________________________________
indiana-discuss mailing list
[email protected]
http://opensolaris.org/mailman/listinfo/indiana-discuss
