From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Tobias Holst <tobby@tobby.eu>, <linux-btrfs@vger.kernel.org>
Subject: Re: general thoughts and questions + general and RAID5/6 stability?
Date: Wed, 24 Sep 2014 09:08:07 +0800 [thread overview]
Message-ID: <54221977.9040707@cn.fujitsu.com> (raw)
In-Reply-To: <CAGwxe4iqZY-GB3tREyqU0O4rkLk0_+oBdft1pRzaTxbZkr-JbQ@mail.gmail.com>
-------- Original Message --------
Subject: Re: general thoughts and questions + general and RAID5/6 stability?
From: Tobias Holst <tobby@tobby.eu>
To: <linux-btrfs@vger.kernel.org>
Date: 2014年09月23日 22:24
> If it is unknown, which of these options have been used at btrfs
> creation time - is it possible to check the state of these options
> afterwards on a mounted or unmounted filesystem?
For mounted fs, sysfs can be used to see the feature enabled:
/sys/fs/btrfs/<UUID>/features/
For unmounted fs, maybe not the best one, btrfs-show-super can show the
incompat_flags in hex,
and we can check <kernel tree>/fs/btrfs/ctree.h for
BTRFS_FEATURE_INCOMPAT_## for the bits
and calculate by hand...
(Would it be better to add human readable output for btrfs-show-super?)
Thanks,
Qu
>
>
> 2014-09-23 15:38 GMT+02:00 Austin S Hemmelgarn <ahferroin7@gmail.com>:
>> Well, running 'mkfs.btrfs -O list-all' with 3.16 btrfs-progs gives the following list of features:
>> mixed-bg - mixed data and metadata block groups
>> extref - increased hard-link limit per file to 65536
>> raid56 - raid56 extended format
>> skinny-metadata - reduced size metadata extent refs
>> no-holes - no explicit hole extents for files
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-24 1:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 20:50 general thoughts and questions + general and RAID5/6 stability? William Hanson
2014-09-20 9:32 ` Duncan
2014-09-22 20:51 ` Stefan G. Weichinger
2014-09-23 12:08 ` Austin S Hemmelgarn
2014-09-23 13:06 ` Stefan G. Weichinger
2014-09-23 13:38 ` Austin S Hemmelgarn
2014-09-23 13:51 ` Stefan G. Weichinger
2014-09-23 14:24 ` Tobias Holst
2014-09-24 1:08 ` Qu Wenruo [this message]
[not found] ` <CAGwxe4i2gQXSPiBGXbUKWid3o1tmD_+YtbOj=GQ11vzGx8CuTw@mail.gmail.com>
2014-09-23 14:47 ` Austin S Hemmelgarn
2014-09-23 15:25 ` Kyle Gates
2014-09-25 7:15 ` Stefan G. Weichinger
-- strict thread matches above, loose matches on Subject: below --
2014-08-31 4:02 Christoph Anton Mitterer
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=54221977.9040707@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tobby@tobby.eu \
/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.