> 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 z/b80nd/
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
zfs-discuss@opensol
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 wh
I've hit the problem myself recently, and mounting the filesystem cleared
something in the brains of ZFS and alowed me to snapshot.
http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg00812.html
PS: I'll use Google before asking some questions, a'la (C) Bart Simpson
That's how I found yo
Hello,
I'm trying to track down a problem with taking zfs snapshots. On
occasion the zfs command will report:
cannot snapshot '': dataset is busy
The problem is, I don't know what causes zfs to think the data set is
"busy". Anyone out there know what constitutes a busy dataset?
I did some testi
