From: Christian Robert <christian.robert@polymtl.ca>
To: linux-btrfs@vger.kernel.org
Subject: btrfs: Probably the larger filesystem I will see for a long time
Date: Fri, 18 May 2012 23:03:28 -0400 [thread overview]
Message-ID: <4FB70D80.4030300@polymtl.ca> (raw)
Probably the larger filesystem I will ever see. Tryed 8 Exabytes but it failed.
[root@CentOS6-A:/root] # df
Filesystem 1K-blocks Used Available Use% Mounted
/dev/mapper/vg01-root 17915884 11533392 5513572 68% /
/dev/sda1 508745 140314 342831 30% /boot
/dev/mapper/data_0 66993872 1644372 61994060 3% /mnt/data_0
/dev/mapper/data_1 7881299347898368 508360 7881248224091896 1% /mnt/data_1
[root@CentOS6-A:/root] # df -h
Filesystem Size Used Avail Use% Mounted
/dev/mapper/vg01-root 18G 11G 5.3G 68% /
/dev/sda1 497M 138M 335M 30% /boot
/dev/mapper/data_0 64G 1.6G 60G 3% /mnt/data_0
/dev/mapper/data_1 7.0E 497M 7.0E 1% /mnt/data_1
[root@CentOS6-A:/root] # df -Th
Filesystem Type Size Used Avail Use%
/dev/mapper/vg01-root ext4 18G 11G 5.3G 68%
/dev/sda1 ext4 497M 138M 335M 30%
/dev/mapper/data_0 ext4 64G 1.6G 60G 3%
/dev/mapper/data_1 btrfs 7.0E 499M 7.0E 1%
[root@CentOS6-A:/root] #
[root@CentOS6-A:/root] # uname -rv
3.4.0-rc7+ #23 SMP Wed May 16 20:20:47 EDT 2012
made with a dm-thin device sitting on a device pair composed of (metadata 256Megs and data 23 Gigs)
running on my laptop at home.
yes, this is 7 Exabytes or 7,168 Petabytes or ( 7,340,032 Terabytes ) or 7,516,192,768 Gigabytes.
please do not answer, it is just a statement of a fact at 3.4-rc7 (was not working at 3.4-rc3 if I remember).
Xtian.
next reply other threads:[~2012-05-19 3:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-19 3:03 Christian Robert [this message]
2012-05-22 17:17 ` Which is the maximum files size in BTRFS ? [was Re: btrfs: Probably the larger filesystem I will see for a long time] Goffredo Baroncelli
2012-05-22 19:48 ` Goffredo Baroncelli
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=4FB70D80.4030300@polymtl.ca \
--to=christian.robert@polymtl.ca \
--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).