* David Magda (dma...@ee.ryerson.ca) wrote: > On Sep 25, 2009, at 16:39, Glenn Lagasse wrote: > > >There's very little you can safely move in my experience. /export > >certainly. Anything else, not really (though ymmv). I tried to > >create > >a seperate zfs dataset for /usr/local. That worked some of the time, > >but it also screwed up my system a time or two during > >image-updates/package installs. > > I'd be very surprised (disappointed?) if /usr/local couldn't be > detached from the rpool. Given that in many cases it's an NFS mount, > I'm curious to know why it would need to be part of the rpool. If it > is a 'dependency' I would consider that a bug.
It can be detached, however one issue I ran in to was packages which installed into /usr/local caused problems when those packages were upgraded. Essentially what occurred was that /usr/local was created on the root pool and upon reboot caused the filesystem service to go into maintenance because it couldn't mount the zfs /usr/local dataset on top of the filled /usr/local root pool location. I didn't have time to investigate into it fully. At that point, spinning /usr/local off into it's own zfs dataset just didn't seem worth the hassle. Others mileage may vary. -- Glenn _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
