Yes, it seems that mounting it and unmounting it with the zfs command clears
the condition and allows the data set to be destroyed. Seems this is a bug in
zfs, or at least an annoyance. I verified with fuser that no processes were
using the file system.
Now, what I'd really like to know, is
Hmm, actually, not.
I just ran into a dataset where the mount/unmount doesn't clear the condition.
I still get dataset is busy when attempting to destroy it.
This message posted from opensolaris.org
___
zfs-discuss mailing list
what causes a dataset to get into this state?
while I'm not exactly sure, I do have the steps leading up to when
I saw it trying to create a snapshot. ie:
10 % zfs snapshot z/b80nd/[EMAIL PROTECTED]
cannot create snapshot 'z/b80nd/[EMAIL PROTECTED]': dataset is busy
13 % mount -F zfs
Hello All,
In a moment of insanity I've upgraded from a 5200+ to a Phenom 9600 on my
zfs server and I've had a lot of problems with hard hangs when accessing the
pool.
The motherboard is an Asus M2N32-WS, which has had the latest available BIOS
upgrade installed to support the Phenom.
All;
I have a 24-disk SATA array attached to an HP DL160 with a LSI 3801E for the
controller. We've been seeing errors that look like:
WARNING: /[EMAIL PROTECTED],0/pci8086,[EMAIL PROTECTED]/pci8086,[EMAIL
PROTECTED],3/pci1000,[EMAIL PROTECTED] (mpt0);
Disconnected command timeout for
Today, suddenly, without any apparent reason that I can find, I'm
getting panic's during zpool import. The system paniced earlier today
and has been suffering since. This is snv_43 on a thumper. Here's the
stack:
panic[cpu0]/thread=99adbac0: assertion failed: ss != NULL, file:
