From owner-freebsd-bugs@freebsd.org Wed Oct 28 15:26:01 2015 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16D6CA20CA8 for ; Wed, 28 Oct 2015 15:26:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E98B31F2B for ; Wed, 28 Oct 2015 15:26:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9SFQ0gt034483 for ; Wed, 28 Oct 2015 15:26:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 204093] [zfs] Overflowing the max path for ZFS snapshot automount leaves the zfs in an busy state Date: Wed, 28 Oct 2015 15:26:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: matthew@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Oct 2015 15:26:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204093 Bug ID: 204093 Summary: [zfs] Overflowing the max path for ZFS snapshot automount leaves the zfs in an busy state Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: matthew@FreeBSD.org To reproduce, set up a zfs with snapshots like so: {{{ # zfs list -t all -r tank/.......1 NAME USED AVAIL REFER MOUNTPOINT tank/.......1 19K 769G 19K /.......1 tank/.......1@....3.........4.........5.........6.........7.........8........ 0 - 19K - tank/.......1@....3.........4.........5.........6.........7.........8......... 0 - 19K - tank/.......1@....3.........4.........5.........6.........7.........8.........9.........0 0 - 19K - }}} These names are carefully calculated to hit or exceed the 88 character limit on mountpoint path lengths when the snapshots are automounted Now, doing something that would cause the snapshots to automount leads to the expected 'name too long' errors: {{{ # find /.......1/.zfs/snapshot /.......1/.zfs/snapshot find: /.......1/.zfs/snapshot/....3.........4.........5.........6.........7.........8.........: File name too long /.......1/.zfs/snapshot/....3.........4.........5.........6.........7.........8........ /.......1/.zfs/snapshot/....3.........4.........5.........6.........7.........8......../aaa /.......1/.zfs/snapshot/....3.........4.........5.........6.........7.........8......../aaa/bbb /.......1/.zfs/snapshot/....3.........4.........5.........6.........7.........8......../aaa/bbb/ccc find: /.......1/.zfs/snapshot/....3.........4.........5.........6.........7.........8.........9.........0: File name too long }}} This is all as expected. Problem is that now the tank/.......1 zfs is left in a busy state: {{{ # zfs destroy -r tank/.......1 cannot unmount '/.......1': Device busy }}} Needs a forced unmount to do anything with it: {{{ # zfs umount -f /.......1 }}} I'd expect that other than an error message there wouldn't be any side effects of failing to automount a snapshot due to overflowing the maximum allowed path length. -- You are receiving this mail because: You are the assignee for the bug.