From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id B0642DF87 for ; Wed, 20 Apr 2022 18:26:44 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A9B97E2F1 for ; Wed, 20 Apr 2022 18:26:14 +0200 (CEST) Received: from mail-yw1-x1133.google.com (mail-yw1-x1133.google.com [IPv6:2607:f8b0:4864:20::1133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 0A15EE2E0 for ; Wed, 20 Apr 2022 18:26:14 +0200 (CEST) Received: by mail-yw1-x1133.google.com with SMTP id 00721157ae682-2ef5380669cso23828257b3.9 for ; Wed, 20 Apr 2022 09:26:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=IKsSgFLu2/1hohRy2+9k+QY84VCm2kGQKHCwj4//qdw=; b=DH0LhsfSOq7e2sya5gMr1GTLxZr3WhR+DJ7JqGgGLlyz0VqkcwNTBicF1xyjQvWhQL kyq/upnLgj95nu3m9OtP1dSDC9hLrAduWTFC/LkRhtXolf+bMBQidOhrxNz/zeOowdwC Tb73vEZR2izrtqjE/IWhbLEwOIDL4K09nEekeCVcSPDrHac1V4UP7JMM5AtBi6NnwESH DhBbJI6CLm0O/4WZzFsko1UmSh4p3tdzN78NxR8W56AAIo8GPZjivyM6yw51qscKJRdg OtvjxKqeRsMBENjuRg1vCqTLF4EvSnt6bd/uqVT30MEiqm1B50qVtc71nxiZRVSO7smA 9vxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=IKsSgFLu2/1hohRy2+9k+QY84VCm2kGQKHCwj4//qdw=; b=Y8f5V0vWe/nUixHHaqtNn14cnGyvbc3t1DWigAb0aX9QoucYP1u42QkiyUqrj8XeFP DJQ0iaAtSBAfayymmo5sEMZTLZ67hp+B2yx93uc9J1FZNR4HDundMxehDswKifflTbSe 0jKzWYvcOqYeZvMqL9mQonWJWbWob6x/ufHc9zBaVV0OmyMvXU7cUSTY/ler1QgDXPhu TpPan1K+OlgS93I4kTHtp4XKeff9kDkaS4bP9zHnIsdWiRqinbmJjdH3ADlJ6AIHNh+X aiWIYBbngwoEEFH/lbJIJ9ZFb2fTfanbeY6vmhB7kI3TBHnuzKsCggL0PeNu6Iyfhexd gK7g== X-Gm-Message-State: AOAM532QQs3QUUD9WVN/hj/KHPSxEWaQtv1Z40/OiLzLniMtgkZb4pka ft4JZCBhJdHKEOAulr8j3GiM9gLWqc/4rhtBThaXS4Kwv50= X-Google-Smtp-Source: ABdhPJx2QcGBqP6PiceRbr0VtKoU3FZqeyEmVJotROIJ184d4Mo6nOnexNfF8IzNPTThWIfs+vfNcfu0XUZnAq2HdmU= X-Received: by 2002:a81:144a:0:b0:2f4:cd91:76ca with SMTP id 71-20020a81144a000000b002f4cd9176camr1203236ywu.417.1650471966347; Wed, 20 Apr 2022 09:26:06 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: GM Date: Wed, 20 Apr 2022 17:25:55 +0100 Message-ID: To: Proxmox VE user list X-SPAM-LEVEL: Spam detection results: 0 AWL 0.671 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_ENVFROM_END_DIGIT 0.25 Envelope-from freemail username ends in digit FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_MESSAGE 0.001 HTML included in message RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] Data limits not being respected on zfs vm volume X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2022 16:26:44 -0000 > > Trouble is, it kept expanding past 256GB, using up all the free space on > the host boot drive. This morning everything was down and I had to > delete the volume to get a functioning system. Just to add up onto this, you could get around this from happening in the future by setting a "reservation" or "refreservation" to "rpool/ROOT/pve-1" dataset (man zfsprops for more details).