From: Roman Mamedov <rm@romanrm.net>
To: linux-btrfs@vger.kernel.org
Subject: "error inheriting props for ino": Btrfs "compression" property
Date: Wed, 25 Jul 2018 21:16:36 +0500 [thread overview]
Message-ID: <20180725211636.36d66800@natsu> (raw)
Hello,
On two machines I have subvolumes where I backup other hosts' root filesystems
via rsync. These subvolumes have the +c attribute on them.
During the backup, sometimes I get tons of messages like these in dmesg:
[Wed Jul 25 20:58:22 2018] BTRFS error (device dm-8): error inheriting props for ino 1213720 (root 1301): -28
[Wed Jul 25 20:58:22 2018] BTRFS error (device dm-8): error inheriting props for ino 1213723 (root 1301): -28
[Wed Jul 25 20:58:22 2018] BTRFS error (device dm-8): error inheriting props for ino 1213724 (root 1301): -28
[Wed Jul 25 20:58:22 2018] BTRFS error (device dm-8): error inheriting props for ino 1213725 (root 1301): -28
# btrfs inspect inode-resolve 1213720 .
./gemini/lib/modules/4.14.58-rm2+/kernel/virt
This seems to be related to the "compression" property in Btrfs:
# btrfs property get ./gemini/lib/modules/4.14.58-rm2+/
compression=zlib
# btrfs property get ./gemini/lib/modules/4.14.58-rm2+/kernel/virt
(no output)
Why would it fail like that? This does seem harmless, but the messages are annoying and it's puzzling why
this happens in the first place.
--
With respect,
Roman
reply other threads:[~2018-07-25 17:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180725211636.36d66800@natsu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.