On Mon, Jan 4, 2010 at 8:59 PM, Richard Elling <richard.ell...@gmail.com> wrote: > > On Jan 4, 2010, at 6:40 AM, Carl Rathman wrote: > >> I have a zpool raidz1 array (called storage) that I created under snv_118. >> >> I then created a zfs filesystem called storage/vmware which I shared >> out via iscsi. >> >> >> >> I then deleted the vmware filesystem, using 'zpool destroy -f >> storage/vmware' -- which resulted in heavy disk activity, and then >> hard locked the system after 10 minutes. >> >> I rebooted the machine, but was unable to boot. The machine would hang >> on Reading ZFS Configuration: - (the stick wouldn't even spin.) >> >> I was able to work around that by booting to a live CD, and deleting >> the zfs cache on my rpool. > > [clicked the wrong button] > If you destroy the pool, then why try to import? > -- richard > >> zpool import sees my raidz1 array, but if I try 'zpool import -f >> storage', I get the same behavior of heavy disk activity for >> approximately 10 minutes, then a hard lock. >> >> >> Any clues on this one? >> >> Thanks, >> Carl >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss@opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > >
I didn't mean to destroy the pool. I used zpool destroy on a zvol, when I should have used zfs destroy. When I used zpool destroy -f mypool/myvolume the machine hard locked after about 20 minutes. I don't want to destroy the pool, I just wanted to destroy the one volume. -- Which is why I now want to import the pool itself. Does that make sense? Thanks, Carl _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
