Date: Wed, 25 May 2011 13:58:45 -0400 From: Dave Cundiff <syshackmin@gmail.com> To: Pawel Jakub Dawidek <pjd@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: ZFS promote failure Message-ID: <BANLkTikDk1SGu1yeofsxTgaxxAfjzDLwoA@mail.gmail.com> In-Reply-To: <20110525142128.GH1877@garage.freebsd.pl> References: <BANLkTi=QpSt3b0h8OTyni%2B3JFpRC=7g8ZQ@mail.gmail.com> <20110525142128.GH1877@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 25, 2011 at 10:21 AM, Pawel Jakub Dawidek <pjd@freebsd.org> wrote: > On Wed, May 11, 2011 at 11:50:51AM -0400, Dave Cundiff wrote: >> Hello, >> >> I'm seeing a strange problem trying to use zfs promote. >> >> [root@san2]# zfs snapshot san/sr@snap >> [root@san2]# zfs clone san/sr@snap san/sr5 >> [root@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. > Hi, I was using 8.1-RELEASE and upgraded to 8.2-RELEASE to make see if it improved. [root@san2 ~]# zpool upgrade This system is currently running ZFS pool version 15. All pools are formatted using this version. [root@san2 ~]# zfs upgrade This system is currently running ZFS filesystem version 4. All filesystems are formatted with the current version. [root@san2 ~]# uname -a FreeBSD san2.a2hosting.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 root@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. Thanks, -- Dave Cundiff System Administrator A2Hosting, Inc http://www.a2hosting.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTikDk1SGu1yeofsxTgaxxAfjzDLwoA>