Now, so my humble guess, I need to know the commands
to be run in the new install to de-associate c0d0s7
from the old install and re-associate this drive with
the new install.
All this probably happened through the '-f' in 'zpool
create -f newhome c0d0s7'; which seemingly takes
precedence
Get the content of c0d1s1 to c0d0s7 ?
c0d1s1 is pool home and active; c0d0s7 is not
active.
I have not tried this particular use case, but I think this is a case for zfs
send and zfs receive. You'd create a new pool containing only c0d0s7 and
do something like this, assuming your original
Both work properly. Half of the job done; now I have
the new home mounted, but inactive. So I can rm -Rf *
or similar there; in order to 'cp -a' the content of
the old home to the new home.
Still the other half is unresolved: How do I mount
the old home which is in no fstab (mnttab), on
Quick question about the interaction of ZFS filesystem compression and the
filesystem cache. We have an Opensolaris (actually Nexenta alpha-6) box
running RRD collection. These files seem to be quite compressible. A test
filesystem containing about 3,000 of these files shows a compressratio
Looking at the source code overview, it looks like
the compression happens underneath the ARC layer,
so by that I am assuming the uncompressed blocks are
cached, but I wanted to ask to be sure.
Thanks!
-Andy
Yup, your assumption is correct. We currently do
compression below the
Be careful here. If you are using files that have no
data in them yet
you will get much better compression than later in
life. Judging by
the fact that you got only 12.5x, I suspect that your
files are at
least partially populated. Expect the compression to
get worse over
time.
I do
