ZFS promote failure
syshackmin at gmail.com
Wed May 25 17:58:48 UTC 2011
On Wed, May 25, 2011 at 10:21 AM, Pawel Jakub Dawidek <pjd at freebsd.org> wrote:
> On Wed, May 11, 2011 at 11:50:51AM -0400, Dave Cundiff wrote:
>> I'm seeing a strange problem trying to use zfs promote.
>> [root at san2]# zfs snapshot san/sr at snap
>> [root at san2]# zfs clone san/sr at snap san/sr5
>> [root at san2]# zfs promote san/sr5
>> cannot promote 'san/sr5': dataset is busy
>> Being a freshly created dataset I'm not sure how it would be busy. Are
>> there any caveats to using zfs promote on zvols? The snapshots are of
>> ext3 formatted zvols. I don't really need to promote them but wanted
>> to in case I needed to destroy the source for some reason.
> Which FreeBSD version is this? I just tried it on 9-CURRENT with ZFSv28
> and it works just fine, even if I've file systems mounted on top of
> those ZVOLs.
I was using 8.1-RELEASE and upgraded to 8.2-RELEASE to make see if it improved.
[root at san2 ~]# zpool upgrade
This system is currently running ZFS pool version 15.
All pools are formatted using this version.
[root at san2 ~]# zfs upgrade
This system is currently running ZFS filesystem version 4.
All filesystems are formatted with the current version.
[root at san2 ~]# uname -a
FreeBSD san2.a2hosting.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb
17 02:41:51 UTC 2011
root at mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
Little more detail. The zvol that is the source of the clone is an
image I use for all my filesystems. I was able to create one clone and
promote it. However, when I tried to do it a second time I received
that error. Can you only have 1 promoted clone per source? I don't
really need to promote them. I just wanted to be able to delete the
source image once the box was full. If it has a ton of associated
clones it'll be stuck there forever.
More information about the freebsd-questions