linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Lohmann <marcel.lohmann@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs on LVM: Out of space
Date: Thu, 9 Sep 2010 12:54:52 +0200	[thread overview]
Message-ID: <AANLkTik1cXM0uwhwJSFNKMT1aiyRRLvNhYNFUGw8-zvt@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=EyKFr_QCAoWtM=wZ8EnijcDuDfjgiyaE+dnuc@mail.gmail.com>

2010/9/9 Zhu Yanhai <zhu.yanhai@gmail.com>:
> 200B ~ 2000B is really too small to the modern hard disks (some of them
> already have 4KB-sectors instead of 512B).

I know. But I thought that btrfs is the best FS for handling that.
Besides other storage methods than keeping small files on a
filesystem.
This is why I wanted to give it a try. It's currently just an
experiment for me to evaluate best practices.

> Besides, currectly Btrfs doesn't play quite well with such small files, you may

> had a patch for it, IIRC. Here it is:
> http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg05292.html
> I don't know whether it has been in the kernel you are using.

Looking real quick on the patch and the git commits I would confirm
that this is already in the kernel 2.6.35 (which Ubuntu 10.10 uses).
So there is a good chance to have a "repaired" filesystem when I
recreate it.

Marcel

  reply	other threads:[~2010-09-09 10:54 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
2010-09-09  9:52         ` Zhu Yanhai
2010-09-09 10:54           ` Marcel Lohmann [this message]
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=AANLkTik1cXM0uwhwJSFNKMT1aiyRRLvNhYNFUGw8-zvt@mail.gmail.com \
    --to=marcel.lohmann@googlemail.com \
    --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).