All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: 2 PB filesystem ok?
Date: Wed, 1 May 2024 16:16:26 +0200	[thread overview]
Message-ID: <ZjJOuiu0o1PqV3jA@ws> (raw)
In-Reply-To: <20240501085012.GA393383@tik.uni-stuttgart.de>

[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]

On 2024-05-01 10:50:12 +0200, Ulli Horlacher wrote:
> On Mon 2024-04-29 (12:34), Johannes Thumshirn wrote:
>
> > I have used 2PB filesystems in my RAID Stripe Tree test environment, but
> > for practical uses, I suggest you to enable the block-group tree feature
> > during mkfs time.
>
> I cannot find such an option in man-page for mkfs.btrfs

    $ mkfs.btrfs  -O list-all
    Filesystem features available:
    mixed-bg            - mixed data and metadata block groups (compat=2.6.37, safe=2.6.37)
    quota               - quota support (qgroups) (compat=3.4)
    extref              - increased hardlink limit per file to 65536 (compat=3.7, safe=3.12, default=3.12)
    raid56              - raid56 extended format (compat=3.9)
    skinny-metadata     - reduced-size metadata extent refs (compat=3.10, safe=3.18, default=3.18)
    no-holes            - no explicit hole extents for files (compat=3.14, safe=4.0, default=5.15)
    free-space-tree     - free space tree (space_cache=v2) (compat=4.5, safe=4.9, default=5.15)
    raid1c34            - RAID1 with 3 or 4 copies (compat=5.5)
    zoned               - support zoned devices (compat=5.12)
    block-group-tree    - block group tree to reduce mount time (compat=6.1)

So I believe it would be `mkfs.btrfs -O block-group-tree ...'.

>
>
> --
> Ullrich Horlacher              Server und Virtualisierung
> Rechenzentrum TIK
> Universitaet Stuttgart         E-Mail: horlacher@tik.uni-stuttgart.de
> Allmandring 30a                Tel:    ++49-711-68565868
> 70569 Stuttgart (Germany)      WWW:    https://www.tik.uni-stuttgart.de/
> REF:<6609017e-8931-4559-b613-4b3e28d9fb48@wdc.com>
>

--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-05-01 14:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-28 23:31 2 PB filesystem ok? Ulli Horlacher
2024-04-29 10:11 ` Andrea Gelmini
2024-04-29 12:34 ` Johannes Thumshirn
2024-05-01  8:50   ` Ulli Horlacher
2024-05-01 14:16     ` Tomas Volf [this message]
2024-05-01 18:19       ` Ulli Horlacher
2024-05-01 19:47         ` Martin Steigerwald
2025-06-28 17:15           ` Ulli Horlacher

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=ZjJOuiu0o1PqV3jA@ws \
    --to=~@wolfsden.cz \
    --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.