From: "Tamás Gulácsi" <gt-dev@gthomas.homelinux.org>
To: Marcel Lohmann <marcel.lohmann@googlemail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs on LVM: Out of space
Date: Thu, 9 Sep 2010 11:37:08 +0200 [thread overview]
Message-ID: <AANLkTimjz0Bo_Vz7aapSfZXFJCsz7Ynm0uhykHhMrBdw@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikujoMMHiwhgBns7W462pPYSsTywY6uHCw2vUCD@mail.gmail.com>
You can try "-l" option of mkfs.btrfs to have all the small files
packed in the metadata, not extents.
GThomas
2010/9/9 Marcel Lohmann <marcel.lohmann@googlemail.com>:
> 2010/9/9 Zhu Yanhai <zhu.yanhai@gmail.com>:
>> 2010/9/9 Marcel Lohmann <marcel.lohmann@googlemail.com>:
>>> 2010/9/8 Zhu Yanhai <zhu.yanhai@gmail.com>:
>>> But if it is neccessary to "drop" that duplicate metadata, how can =
I
>>> arrange this afterwards. And if it is done, then I would have reduc=
ed
>>> the Metadata size, but will there really be more space for Data? Wh=
ere
>>> is the remaining space from 77 GB to 130 GB?
>>
>> 53 * 2 + 24 =3D 130. The size of Metadata reported by "btrfs filesys=
tem df"
>> is 53GB, however it occupies 53 * 2 =3D 106GB on 'disk' physically.
>> So yes, there will be more space for Data.
>>
>
> Perfect, great. This sounds strange on the first sight because it doe=
s
> not show anywhere that one has to double the metadata. Or better: tha=
t
> it is currently doubled.
> So I know what I have to do now. I will drop the partition and create=
it again.
> There is then still the problem that I have twice the size of metadat=
a
> than real data. But I guess that is due to the high number of very
> small files (current estimate is 1440*50000 files with around 200Byte=
s
> to 2000Bytes). On the other hand there is only twice the size reserve=
d
> and actually used a bit more that the real data.
>
> Many thanks for make that clear to me.
>
> Marcel
> --
> 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 =C2=A0http://vger.kernel.org/majordomo-info.ht=
ml
>
--
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:[~2010-09-09 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 11:18 btrfs on LVM: Out of space Marcel Lohmann
2010-09-08 14:53 ` Zhu Yanhai
2010-09-08 20:35 ` Marcel Lohmann
2010-09-09 2:15 ` Zhu Yanhai
2010-09-09 9:23 ` Marcel Lohmann
2010-09-09 9:37 ` Tamás Gulácsi [this message]
2010-09-09 9:52 ` Zhu Yanhai
2010-09-09 10:54 ` Marcel Lohmann
2010-09-10 19:46 ` Marcel Lohmann
2010-09-17 15:29 ` Johannes Hirte
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=AANLkTimjz0Bo_Vz7aapSfZXFJCsz7Ynm0uhykHhMrBdw@mail.gmail.com \
--to=gt-dev@gthomas.homelinux.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcel.lohmann@googlemail.com \
/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).