e".
Ok, thanks for the explanation :-)
--
Alan Burlison
--
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
NAME USED AVAIL REFER MOUNTPOINT
pool/ROOT 5.58G 53.4G18K legacy
What's the legacy mount for? Is it related to zones?
thanks,
--
Alan Burlison
--
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
ly.
If there was a '-nomount' flag to zfs receive, snapshotting & saving
a pool would be just 2 commands.
Looks like a RFE is needed to me...
--
Alan Burlison
--
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Alan Burlison wrote:
> So how do I tell zfs receive to create the new filesystems in pool3, but
> not actually try to mount them?
This is even more of an issue with ZFS root - as far as I can tell it's
impossible to recursively back up all the filesystems in a root pool
because of
& ZFS boot don't mix.
--
Alan Burlison
--
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Mark J Musante wrote:
> Alan, can you point me at your machine (if it's on SWAN)? I'd like to
> see what's going on in there.
Might be easiest to use sun shared shell to get you access...
--
Alan Burlison
--
___
zfs-discuss mai
Mark J Musante wrote:
> As a workaround, you can pre-create the swap & dump zvols. E.g.:
>
> zfs create -V 512m {pool}/swap
> zfs create -V 2g {pool}/dump
>
> If LU sees that the zvols already exist, it assumes they are correctly
> sized.
Nice tip, than
Enda O'Connor wrote:
> probably
> 6722767 lucreate did not add new BE to menu.lst ( or grub )
Yeah, I found that bug, added A CR & bumped the priority. Unfortunatrly
there's no analysis or workaround in the bug, so I've no idea what the
real probl
one point. I've tried blitzing and reinstalling LU entirely - still no joy.
--
Alan Burlison
--
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
x27;/home4': directory is not empty
So how do I tell zfs receive to create the new filesystems in pool3, but
not actually try to mount them?
--
Alan Burlison
--
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailm
next step:
8. copy the ZFS BE into the new pool made from the UFS BE
because I can't get LU to create the BE in a different ZFS pool.
--
Alan Burlison
--
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
work, because LU wants to create both swap & dump ZFS
filesystems in there too, my machine has 16Gb of memory and the slice is
8Gb - so there isn't enough space & LU throws a cog. Which is why I
wanted to get it to use the old swap partition in
want to
> continue to refine how zfs works as a root file system.
I'm really liking what I see so far, it's just a question of getting my
head around the best way of setting things up, and figuring out the
easiest way of migrating.
--
Alan Burlison
--
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
ly using swap or dump,
no space is actually used (other than the zfs filesystem overhead) - is
that correct?
I'm now coming up with a mad scheme involving ZFS boot, a USB disk,
string and prayer to enable me to get rid of the old UFS root & swap
slices on my root disk and
wap & dump.
Basically I want to migrate my root filesystem from UFS to ZFS and leave
everything else as it it, there doesn't seem to be a way to do this.
--
Alan Burlison
--
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I'm upgrading my B92 UFS-boot system to ZFS root using Live Upgrade. It
appears to work fine so far, but I'm wondering why it allocates a ZFS
filesystem for swap when I already have a dedicated swap slice.
Shouldn't it just use any existing swap slice rather than creating a ZFS
16 matches
Mail list logo
