From: Roman Mamedov <rm@romanrm.net>
To: linux-btrfs@vger.kernel.org
Subject: Issue remounting from compress-force to compress
Date: Mon, 14 Oct 2024 18:24:16 +0500 [thread overview]
Message-ID: <20241014182416.13d0f8b0@nvm> (raw)
Hello,
Just faced this when trying to change a mounted FS from compress-force to just compress.
Initial state:
# mount | grep btrfs
/dev/mapper/wd-p1 on /mnt/p1 type btrfs (rw,relatime,compress-force=zstd:9,discard=async,space_cache=v2,subvolid=5,subvol=/)
Remounting:
# mount /mnt/p1 -o remount,compress=zstd:9
But no effect:
# mount | grep btrfs
/dev/mapper/wd-p1 on /mnt/p1 type btrfs (rw,relatime,compress-force=zstd:9,discard=async,space_cache=v2,subvolid=5,subvol=/)
OK, remounting to no compression:
# mount /mnt/p1 -o remount,compress-force=none
Success:
# mount | grep btrfs
/dev/mapper/wd-p1 on /mnt/p1 type btrfs (rw,relatime,discard=async,space_cache=v2,subvolid=5,subvol=/)
Now, I expect to enable just compress:
# mount /mnt/p1 -o remount,compress=zstd:9
But suddenly, compress-force is enabled again instead:
# mount | grep btrfs
/dev/mapper/wd-p1 on /mnt/p1 type btrfs (rw,relatime,compress-force=zstd:9,discard=async,space_cache=v2,subvolid=5,subvol=/)
This is unexpected and seems like a bug.
The only way to achieve what I wanted was:
# mount /mnt/p1 -o remount,compress-force=none,compress=zstd:9
# mount | grep btrfs
/dev/mapper/wd-p1 on /mnt/p1 type btrfs (rw,relatime,compress=zstd:9,discard=async,space_cache=v2,subvolid=5,subvol=/)
Kernel version is 6.8.12-2-pve (Proxmox).
--
With respect,
Roman
next reply other threads:[~2024-10-14 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 13:24 Roman Mamedov [this message]
2024-10-14 15:50 ` Issue remounting from compress-force to compress Filipe Manana
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241014182416.13d0f8b0@nvm \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox