From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: BTRFS extended attributes mounted on a non-extended-attributes compiled kernel
Date: Wed, 11 Dec 2013 17:51:06 +0000 [thread overview]
Message-ID: <l8a8lv$mk7$1@ger.gmane.org> (raw)
What happens if...
I have a btrfs that has utilised posix ACLs / extended attributes and I
then subsequently mount that onto a system that does not have the kernel
modules compiled for those features?
Crash and burn?
Or are the extra filesystem features benignly ignored until remounted on
the original system with all the kernel modules?
Thanks,
Martin
next reply other threads:[~2013-12-11 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 17:51 Martin [this message]
2013-12-11 19:01 ` BTRFS extended attributes mounted on a non-extended-attributes compiled kernel Hugo Mills
2013-12-11 19:43 ` Chris Mason
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='l8a8lv$mk7$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).