Finally, it's been destroyed!
Last night I turned dedup off and sent the destroy command and simply let it
run over night. Also, I let zpool iostat 30 run as well. It showed no activity
for the first 6-1/2 hours and then a flurry of activity for 13-minutes. That
snapshot is finally gone and th
- "Roy Sigurd Karlsbakk" skrev:
> - "John Balestrini" skrev:
>
> > Yep. Dedup is on. A zpool list shows a 1.50x dedup ratio. I was
> > imagining that the large ratio was tied to that particular snapshot.
> >
> > basie@/root# zpool list pool1
> > NAMESIZE ALLOC FREECAP DEDUP
- "John Balestrini" skrev:
> Yep. Dedup is on. A zpool list shows a 1.50x dedup ratio. I was
> imagining that the large ratio was tied to that particular snapshot.
>
> basie@/root# zpool list pool1
> NAMESIZE ALLOC FREECAP DEDUP HEALTH ALTROOT
> pool1 2.72T 1.55T 1.17T57
On 05/16/10 12:40 PM, John Balestrini wrote:
Yep. Dedup is on. A zpool list shows a 1.50x dedup ratio. I was imagining that
the large ratio was tied to that particular snapshot.
basie@/root# zpool list pool1
NAMESIZE ALLOC FREECAP DEDUP HEALTH ALTROOT
pool1 2.72T 1.55T 1.17T
Yep. Dedup is on. A zpool list shows a 1.50x dedup ratio. I was imagining that
the large ratio was tied to that particular snapshot.
basie@/root# zpool list pool1
NAMESIZE ALLOC FREECAP DEDUP HEALTH ALTROOT
pool1 2.72T 1.55T 1.17T57% 1.50x ONLINE -
So, it is possible to t
On 05/16/10 06:52 AM, John Balestrini wrote:
Howdy All,
I've a bit of a strange problem here. I have a filesystem with one snapshot
that simply refuses to be destroyed. The snapshots just prior to it and just
after it were destroyed without problem. While running the zfs destroy command
on th
> Has anyone seen this type of problem? Any ideas?
Yeah, I've seen the same. Tried to remove a dataset, and it hung on one
snapshot. This was a test server, so I ended up recreating the pool instead of
trying to report a bug about it (hours of time saved, since the debugging
features for ZFS a
Howdy All,
I've a bit of a strange problem here. I have a filesystem with one snapshot
that simply refuses to be destroyed. The snapshots just prior to it and just
after it were destroyed without problem. While running the zfs destroy command
on this particular snapshot, the server becomes more
