From: Hubert Kario <hka@qbs.com.pl>
To: "Fajar A. Nugraha" <list@fajar.net>,
Chris Mason <chris.mason@oracle.com>
Cc: Olivier Bonvalet <btrfs.list@daevel.fr>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-convert processing time
Date: Mon, 20 Feb 2012 15:12:03 +0100 [thread overview]
Message-ID: <2748764.TcFj1pIuO7@k85hala03> (raw)
In-Reply-To: <CAG1y0sevgB0=Y-Sxe_N4zGeZvYp+Pmpjv0q8JeRg22qtkZ0tJw@mail.gmail.com>
Chris: What will btrfs-convert do when it encounters a directory with m=
ore=20
hardlinks than the btrfs limit?
On Monday 20 of February 2012 21:00:34 Fajar A. Nugraha wrote:
> On Mon, Feb 20, 2012 at 8:50 PM, Hubert Kario <hka@qbs.com.pl> wrote:
> > On Monday 20 of February 2012 14:41:33 Olivier Bonvalet wrote:
> >> Lot of small files (like compressed email from Maildir), and lot o=
f
> >> hardlinks, and probably low free space (near 15% I suppose).
> >>=20
> >>=20
> >> So I think I have my answer :)
> >=20
> > Yes, this is probably the worst possible combination.
> >=20
> > Plese keep us updated. Just to have exact numbers for new users.
>=20
> ... although it would probably fail anyway due to btrfs hardlink limi=
t
> in the same directory.
This problem also went through my mind.
Regards,
--=20
Hubert Kario
QBS - Quality Business Software
02-656 Warszawa, ul. Ksawer=F3w 30/85
tel. +48 (22) 646-61-51, 646-74-24
www.qbs.com.pl
--
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:[~2012-02-20 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 12:51 btrfs-convert processing time Olivier Bonvalet
2012-02-20 13:20 ` Hubert Kario
2012-02-20 13:41 ` Olivier Bonvalet
2012-02-20 13:50 ` Hubert Kario
2012-02-20 14:00 ` Fajar A. Nugraha
2012-02-20 14:12 ` Hubert Kario [this message]
2012-02-20 14:29 ` Olivier Bonvalet
2012-02-21 5:51 ` Fajar A. Nugraha
2012-02-22 16:55 ` Olivier Bonvalet
2012-03-30 19:23 ` Olivier Bonvalet
2012-03-31 20:50 ` Hubert Kario
2012-02-20 13:21 ` Hubert Kario
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=2748764.TcFj1pIuO7@k85hala03 \
--to=hka@qbs.com.pl \
--cc=btrfs.list@daevel.fr \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.net \
/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