On Tue, Jan 5, 2010 at 10:12 AM, Richard Elling <richard.ell...@gmail.com> wrote: > On Jan 5, 2010, at 7:54 AM, Carl Rathman wrote: > >> 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. > > This would be a bug. "zpool destroy" should only destroy pools. > Volumes are datasets and are destroyed by "zfs destroy." Using > "zpool destroy -f" will attempt to force unmounts of any mounted > datasets, but volumes are not mounted, per se. Upon reboot, nothing > will be mounted until after the pool is imported. > > >> 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? > > If the pool was destroyed, then you can try to import using -D. > > Are you sure you didn't "zfs destroy" instead? Once the pool is imported, > "zpool history" will show all of the commands issued against the pool. > -- richard > >
Hi Richard, If I could import the pool, I'd love to do a history on it. At this point, if I attempt to import the pool, the machine will have heavy disk activity on the pool for approximately 10 minutes, then the machine will hard lock. This will happen when I boot the machine from its snv_130 rpool, or if I boot the machine from a snv_130 live cd. Thanks, Carl _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
