From owner-freebsd-current@FreeBSD.ORG Fri Aug 14 09:18:53 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 367E3106568B for ; Fri, 14 Aug 2009 09:18:53 +0000 (UTC) (envelope-from artis.caune@gmail.com) Received: from mail-fx0-f224.google.com (mail-fx0-f224.google.com [209.85.220.224]) by mx1.freebsd.org (Postfix) with ESMTP id C04D08FC43 for ; Fri, 14 Aug 2009 09:18:52 +0000 (UTC) Received: by fxm24 with SMTP id 24so1353702fxm.36 for ; Fri, 14 Aug 2009 02:18:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=tIb9YLLU2k/nnUqUTrKkZ/bz08D6D21AsOTkryNDEAk=; b=IDLsy5IIl3ZYwljrtMshw8gyxbB/hzXmLqpWXAxQa4dI06Y8S5k0549xpa/TI9Z0dZ F9O+mulWhlD1zhHWMith50narPGQ3OwGbpBPd2csxerW6AsWV0tgZLnxb1DbvjhfHe3z 52ZB/IF4PPdmsSQQmE69/PGMs21sh7vorSX94= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=IjE/eJ6JhPv29jHEbgyU1NLDt8G82Mv4e8OBMg6eikid8FBqa644hLFdIKJoy1rlqG ufWSUPzyjuzA9xkOets6UcLc339lu2i4nnRQX2gnYTROfSNk9nPSW5Inq1aMapX7M5Ov XqZox8jqk3OgTPXyvWY7NE/lfESwcWtp6j5xE= MIME-Version: 1.0 Received: by 10.103.78.35 with SMTP id f35mr577065mul.89.1250241531576; Fri, 14 Aug 2009 02:18:51 -0700 (PDT) Date: Fri, 14 Aug 2009 12:18:51 +0300 Message-ID: <9e20d71e0908140218h7a65d8c4g4dbe63d905a51ad8@mail.gmail.com> From: Artis Caune To: FreeBSD Current Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: ZFS rollback lock-up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 09:18:53 -0000 Hi, I read in zfs admin guide and could not try this (on amd64 r196047): - Rolling Back a Dataset Without Unmounting - Solaris Express Community Edition, build 80: This release provides the ability to rollback a dataset without unmounting it first. This feature means that zfs rollback -f option is no longer needed to force an umount operation. The -f option is no longer supported, and is ignored if specified. # zfs create tank/rollback-test # echo 1 > /rollback-test/file # zfs snapshot tank/rollback-test@snapshot1 # echo 2 >> /rollback-test/file # zfs rollback tank/rollback-test@snapshot1 # cat /rollback-test/file # zfs destroy tank/rollback-test works great, because file system is not busy, but if I open some file before rollback: # vim /rollback-test/file ^Z # fstat | grep '/rollback-test' root vim 1254 4 /rollback-test 7 -rw-r--r-- 4096 rw # zfs rollback tank/rollback-test@snapshot1 # fg vim offer me to load file because it has changed, and works great, but after rollback I can not list /rollback-test directory and all zfs commands lock up. Reboot also hangs in unkillable processes. After reset I can destroy dataset. Fanny part is that I can even rollback root file system from which I boot. I know it's crazy to "force"-rollback live file system, just interesting why they made such change. -- Artis Caune Everything should be made as simple as possible, but not simpler.