From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9074BECAAA1 for ; Thu, 27 Oct 2022 13:22:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236043AbiJ0NWS (ORCPT ); Thu, 27 Oct 2022 09:22:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41810 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236011AbiJ0NWQ (ORCPT ); Thu, 27 Oct 2022 09:22:16 -0400 Received: from wnew3-smtp.messagingengine.com (wnew3-smtp.messagingengine.com [64.147.123.17]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 30E68176B90 for ; Thu, 27 Oct 2022 06:22:15 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.west.internal (Postfix) with ESMTP id 4E6B92B064C1; Thu, 27 Oct 2022 09:22:14 -0400 (EDT) Received: from imap50 ([10.202.2.100]) by compute3.internal (MEProxy); Thu, 27 Oct 2022 09:22:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= colorremedies.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; t=1666876933; x= 1666884133; bh=mmOJA1iSZhi2wjuraZShkU156wEc3NJ3HcP85KDoyS0=; b=q W15g+twMILNqkDifUm52dl49uz/vuA1qzrO5XKS3uUJ7Bjmzb59+vbZyHY0rjsIy dKjxzraixytg1FLcIuNmjbzPjN++BNOVf0WUNPQ0O4RWRJJ6vWwYTt1iT2N8XQ5c EWErNoEDC5fLB5J1CXdTqxG9Fw+Osbj8kR26zJTppOrKv+jU/MWn3tdhQNTJcOa6 7OlMgF01E5N0uHuFyebPRl5IkXD3YaQF8uAYYvv9GM6nnsL9rUzFtuthwv7BJuVB ThJp1y3I+T05iJl9+fISce0Wqp5Z9ZfEyD+kUJFVvz2vnq4prt2fF1stGya/ehOG oZRgeUdVS23DncV34CNmQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1666876933; x=1666884133; bh=mmOJA1iSZhi2wjuraZShkU156wEc 3NJ3HcP85KDoyS0=; b=bj+bOqLAzSXwWmm0vWMcfBSxTKV6nEGwlegsreAErsnk xpRpZxulHnd3XFkW8EXDd8I8am2M+5exDkJqjjez6S9/TX4mAiqNBajRAE6YlMgj FpQKCywzVemc0MVHyvsF9rDXDZwp1IbG2W3sF6YUowkUZ/UsGc6iYxXtU65f64T+ Si1EU4h8qB53acvBRe3SSUN6osP00jB/svyIP1KqhmRPThVtNTBcwyysbVLUrrtA nKkMJmSuWdu1DzArEMgcZH6VkXSKsd9SSN6oHug+imrmSqgWjikEcDhiyo9AaB0W zkzlgI4voRkxzsrThZNqEaWqEYLJMcEKny3c4DYbxQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrtdeggdeivdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvvefutgesthdtredtreertdenucfhrhhomhepfdevhhhr ihhsucfouhhrphhhhidfuceolhhishhtshestgholhhorhhrvghmvgguihgvshdrtghomh eqnecuggftrfgrthhtvghrnhepgfdvueektdefgfefgfdtleffvdeileetgfefuddtffel ueeiveeiveekhedtheeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomheplhhishhtshestgholhhorhhrvghmvgguihgvshdrtghomh X-ME-Proxy: Feedback-ID: i06494636:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 68C6B1700083; Thu, 27 Oct 2022 09:22:13 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-1087-g968661d8e1-fm-20221021.001-g968661d8 Mime-Version: 1.0 Message-Id: <0f6f1ecb-84d4-4fac-9fcc-5932d5b4f73d@app.fastmail.com> In-Reply-To: References: <3c352b84-c52a-9e01-1ace-6e984e167753@inbox.ru> Date: Thu, 27 Oct 2022 09:21:53 -0400 From: "Chris Murphy" To: "Zygo Blaxell" , "Nemcev Aleksey" Cc: "Btrfs BTRFS" Subject: Re: compsize reports that filesystem uses zlib compression, while I set zstd compression everywhere Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Wed, Oct 26, 2022, at 9:03 PM, Zygo Blaxell wrote: >> And also it's not possible to specify compression level in defragment - so, >> I'll change the level in subvolume properties, defragment with -czstd, and >> change the level back. > > It's not possible to set the level in subvol properties either. Only the > compress= mount option can set the level. $ sudo btrfs property set test compression zstd:1 $ sudo btrfs property get test compression=zstd:1 $ sudo btrfs property set test compression zstd:f $ sudo btrfs property get test compression=zstd:f It's allowing the arbitrary setting of compression values. This is with btrfs-progs 6.0. Progs is being too permissive, it shouldn't silently set invalid values. But then even with valid values, I'm pretty sure right now the kernel ignores the compression properties. -- Chris Murphy