On Wed, Jan 6, 2010 at 12:11 PM, Carl Rathman wrote:
> On Tue, Jan 5, 2010 at 10:35 AM, Carl Rathman wrote:
>> On Tue, Jan 5, 2010 at 10:12 AM, Richard Elling
>> 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
On Tue, Jan 5, 2010 at 10:35 AM, Carl Rathman wrote:
> On Tue, Jan 5, 2010 at 10:12 AM, Richard Elling
> 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 use
On Tue, Jan 5, 2010 at 10:12 AM, Richard Elling
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
>> af
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 on
On Mon, Jan 4, 2010 at 8:59 PM, Richard Elling 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
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' -- w
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' -- w
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 lo
Interesting,
I had assumed the cause of my problem was de-dup because the symptoms are
similar to what others have reported destroying their deduped datasets, but
their system hangs didn't happen for hours while my system hard locks in 3 to 4
minutes. But now you have me thinking because the d
On Mon, Jan 4, 2010 at 4:22 PM, tom wagner wrote:
> Did you happen to set dedup on that zvol that you destroyed? Your symptoms
> sound just like mine. Check out the threads concerning losing a pool after
> destroying a deduped dataset. There's 3 or 4 of them. I get heavy read
> activity for
Did you happen to set dedup on that zvol that you destroyed? Your symptoms
sound just like mine. Check out the threads concerning losing a pool after
destroying a deduped dataset. There's 3 or 4 of them. I get heavy read
activity for about 4 minutes and then the systems just hangs and I can'
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 lo
12 matches
Mail list logo
