Frank Middleton wrote:
I suppose /var/tmp on zfs would never actually write these files unless
they were written synchronously. In the context of this thread, for
those of us with space constrained boot disks/ssds, is it OK to map
/var/tmp to /tmp, and /var/crash, /var/dump, and swap to a separate
data pool in the context of being able to reboot and install new images?
I've been doing so for a long time now with no problems that I know of.
Just wondering what the gurus think...
Moving /var/tmp works OK, I had a system root pool on an CF card and
moved "busy" filesystems off to another pool. I'm not sure which
filesystem caused the problem, but this system was impossible to live
upgrade. swap and dump are volumes, so they can be anywhere (the both
have commands to add/remove devices).
Havn't seen any definitive response regrading /opt, which IMO should
be a good candidate since the installer makes it a separate fs anyway.
Most of /opt can be relocated, but as I said, I was unable to live
upgrade the box. I only moved staroffice and then created filesystems
with mountpoints in /opt before added applications that install to /opt.
See
http://www.sun.com/bigadmin/features/articles/nvm_boot.jsp
--
Ian.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
