From: Roman Mamedov <rm@romanrm.ru>
To: linux-btrfs@vger.kernel.org
Subject: Massive metadata size increase after upgrade from 3.2.18 to 3.4.1
Date: Sat, 9 Jun 2012 01:38:22 +0600 [thread overview]
Message-ID: <20120609013822.6b06a008@natsu> (raw)
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
Hello,
Before the upgrade (on 3.2.18):
Metadata, DUP: total=9.38GB, used=5.94GB
After the FS has been mounted once with 3.4.1:
Data: total=3.44TB, used=2.67TB
System, DUP: total=8.00MB, used=412.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=84.38GB, used=5.94GB
Where did my 75 GB of free space just went?
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2012-06-08 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 19:38 Roman Mamedov [this message]
2012-06-12 17:38 ` Massive metadata size increase after upgrade from 3.2.18 to 3.4.1 Calvin Walton
2012-06-13 10:30 ` Anand Jain
2012-06-14 11:33 ` David Sterba
2012-06-17 15:29 ` Roman Mamedov
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=20120609013822.6b06a008@natsu \
--to=rm@romanrm.ru \
--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).