cannot destroy dataset

[sirdir]

Hi!
I have a problem with the current beta. I deleted 2 datasets via gui. One is gone, but the other is still halfway there:

Code:

Data                                                   179G  2.62T   244K  /mnt/Data

Data/.system                                          5.00M  2.62T  2.58M  legacy

Data/.system/cores                                    1.16M  2.62T  1.16M  legacy

Data/.system/rrd-0bdbce812de04029980bfa28efc2557d      209K  2.62T   209K  legacy

Data/.system/samba4                                    273K  2.62T   273K  legacy

Data/.system/syslog-0bdbce812de04029980bfa28efc2557d   808K  2.62T   808K  legacy

Data/blabla                                             2.21G  2.62T  2.21G  /mnt/Data/blabla

Data/Shared                                            140K  2.62T   140K  /mnt/Data/Shared

Data/Software                                          176G  2.62T   176G  /mnt/Data/Software

freenas-boot                                          2.47G  59.0G    31K  none

freenas-boot/ROOT                                     2.46G  59.0G    31K  none

freenas-boot/ROOT/FreeNAS-9.3-BETA-1415991473          703K  59.0G   906M  /

freenas-boot/ROOT/FreeNAS-9.3-BETA-1416326711          729K  59.0G   906M  /

freenas-boot/ROOT/FreeNAS-9.3-BETA-1416348004          827K  59.0G   906M  /

freenas-boot/ROOT/FreeNAS-9.3-BETA-1416522377          703K  59.0G   906M  /

freenas-boot/ROOT/FreeNAS-9.3-BETA-1416634263-1        966K  59.0G   907M  /

freenas-boot/ROOT/FreeNAS-9.3-BETA-1416866888          956K  59.0G   909M  /

freenas-boot/ROOT/FreeNAS-9.3-BETA-1416953840         2.46G  59.0G   909M  /

freenas-boot/ROOT/default                               97K  59.0G   929M  legacy

freenas-boot/grub                                     8.17M  59.0G  7.79M  legacy

Data/blabla is the one I deleted.
The mountpoint doesn't exist anymore.

zfs destroy Data/blabla

Code:

cannot destroy 'Data/blabla': dataset is busy

Any idea?

 

[sirdir]

hmm, after several reboots it was suddenly gone...

Similar thing happened yesterday btw, that's why I thought I should report it.

 

[dlavigne]

Anything on the problematic dataset such as the system log or a jail?

 

[sirdir]

Anything on the problematic dataset such as the system log or a jail?

No, not as far as I know. lsof didn't show any open file on it. Also there was no mountpoint anymore, so I guess that shouldn't be the problem.

 

[solarisguy]

Where was your .system ? Your output did not show it.

 

[sirdir]

Where was your .system ? Your output did not show it.

Doesn't it? Line 1-12?

 

[sirdir]

Similar things seem to happen sometimes when I try to replicate a snapshot to the 9.3 beta... it's been running all day, most of the time it works, sometimes I get a 'dataset busy' message, too.

 

[sirdir]

guess that's related, now I get:
CRITICAL: Replication Data/blabla -> 192.168.1.41 failed: cannot receive new filesystem stream: destination has snapshots (eg. Data/blabla@auto-20141112.0400-2w) must destroy them to overwrite it Error 33 : Write error : cannot write compressed block

So, something went out of sync after working initially...