From owner-freebsd-bugs@freebsd.org Wed Oct 10 15:16:50 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9AD6010B3C82 for ; Wed, 10 Oct 2018 15:16:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1F3838492F for ; Wed, 10 Oct 2018 15:16:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D525610B3C81; Wed, 10 Oct 2018 15:16:49 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B316C10B3C80 for ; Wed, 10 Oct 2018 15:16:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 547C78492D for ; Wed, 10 Oct 2018 15:16:49 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A215D20F62 for ; Wed, 10 Oct 2018 15:16:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9AFGmNJ063689 for ; Wed, 10 Oct 2018 15:16:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9AFGmCR063677 for bugs@FreeBSD.org; Wed, 10 Oct 2018 15:16:48 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 232152] unrecoverable state after zroot is filled with data to 100%, can't boot, can't import Date: Wed, 10 Oct 2018 15:16:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: petr.fischer@me.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org 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: quoted-printable 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.27 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 15:16:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232152 Bug ID: 232152 Summary: unrecoverable state after zroot is filled with data to 100%, can't boot, can't import Product: Base System Version: 11.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: petr.fischer@me.com My experience on virtual server: I accidentally filled the zroot zpool with data to the 100% of capacity (available ZFS space exactly 0). Then, it's not possible to boot, just because it's not possible to import z= root pool anymore. When I booted from FreeBSD 11.1-RELEASE Install CD ROM (Live CD option), I can't import the zroot pool with: zpool import zroot Command never ends, zpool process is in "tx->tx" state forever, CPU utiliza= tion is 0%, interrupts 0%, idle 100%. When I try to import filled zroot in readonly mode, yes, that works! But in readonly mode, you can't delete data or snapshots. So it looks like game over. Maybe ZFS is not able to do any commit records anymore on 100% filled pool, I don't know... There is only 512MB (+ 1GB swap) on my virtual server, but 2 years without = any problem with ZFS (hourly snapshots, zfs send for backup, everything works l= ike a charm). Is it really that dangerous to fill the zpool with data to 100%? Such a situation will be simple to simulate: 1) install FreeBSD on the ZFS 2) fill some dataset with random data to the 100% of capacity 3) check with zfs command, if there is really 0 bytes available space 4) reboot 5) gameover --=20 You are receiving this mail because: You are the assignee for the bug.=