> It sounds like you can resolve this issue by simply > booting into the new BE and deleting the /fitz > directory and then rebooting and going back into the > new BE. I say this because from your message it > sounds like the data from your zfs filesystem in > /fitz was copied to /fitz in the new BE (instead of > just being mounted in the new BE). BEFORE DELETING > ANYTHING, please make sure /fitz is not a zfs mount > and just a plain directory and therefore just a copy > of what is in your zpool. Be careful, I don't want > you to lose any data.
Haik, Thank you very much. 'zpool list' yeilds NAME SIZE USED AVAIL CAP HEALTH ALTROOT fitz 74.5G 22.9G 51.6G 30% ONLINE - How do I confirm that /fitz is not currently a zfs mountpoint? 'zfs mount' yeilds fitz/home /fitz/home fitz/home/aorchid /fitz/home/aorchid fitz/music /fitz/music fitz/pg /fitz/pg fitz/pictures /fitz/pictures 'ls -la /fitz' yeilds total 85 drwxr-xr-x 7 root sys 512 Sep 20 10:41 . drwxr-xr-x 30 root root 512 Sep 21 18:28 .. --> this is when I ran 'zpool export fitz' drwxr-xr-x 3 root sys 3 Jul 25 12:22 home etc... /etc/vfstab does not have /fitz and umount /fitz returns umount: warning: /fitz not in mnttab umount: /fitz not mounted > Lastly, ZFS people might be interested in the panic > message you get when you boot back into Solaris 10. They are all related to the NVIDIA driver, gfxp, from what I remember from two weeks ago. I am on an Ultra 20. thanks, aric This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
