From: paran@lysator.liu.se (Pär Andersson)
To: Matteo Frigo <athena@fftw.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Mass-Hardlinking Oops
Date: Sat, 17 Oct 2009 00:17:28 +0200 [thread overview]
Message-ID: <87fx9jugp3.fsf@faran.nsc.liu.se> (raw)
In-Reply-To: <87my3urf75.fsf@fftw.org> (Matteo Frigo's message of "Tue, 13 Oct 2009 20:29:02 -0400")
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
Matteo Frigo <athena@fftw.org> writes:
> For the record, the nnmaildir mail backend in Gnus (an Emacs package
> for reading news and email) creates multiple hardlinks to the same
> file in the same directory. I had several thousands hardlinks at one
> time.
Gnus with nnmaildir is what I use. I wanted to test how much performance
and disk space that would be gained with my Maildirs on btrfs, but I hit
this bug instead.
> I am not saying that what Gnus does is particularly smart, but this is
> an example of a real world application that may break under btrfs.
Not smart at all, and the amount of hard links is not the only problem
with nnmaildir. But on other file systems at least it works.
Regards,
Pär Andersson
[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2009-10-16 22:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 13:16 Mass-Hardlinking Oops Raskin Michael
2009-08-03 14:57 ` Chris Mason
2009-08-03 15:00 ` Tomasz Chmielewski
2009-08-03 20:01 ` Mikhail Raskin
2009-10-11 15:05 ` Pär Andersson
2009-10-11 22:43 ` Yan, Zheng
2009-10-12 8:07 ` Tomasz Chmielewski
2009-10-12 12:47 ` Chris Mason
2009-10-13 7:07 ` Florian Weimer
2009-10-13 7:28 ` Yan, Zheng
2009-10-14 0:29 ` Matteo Frigo
2009-10-15 17:55 ` Tracy Reed
2009-10-15 18:27 ` Tomasz Chmielewski
2009-10-15 19:15 ` Oystein Viggen
2009-10-16 22:17 ` Pär Andersson [this message]
2009-10-12 16:16 ` jim owens
2009-10-12 17:09 ` Goffredo Baroncelli
2009-10-12 18:07 ` jim owens
2009-10-12 17:42 ` John Dong
2009-10-12 18:17 ` jim owens
2009-10-12 20:04 ` Chris Mason
2009-10-12 21:51 ` berk walker
2009-10-13 0:31 ` Claudio Martins
2009-10-13 3:42 ` Anthony Roberts
2009-10-13 9:08 ` Brian Brunswick
2009-10-13 17:45 ` Zach Brown
2009-10-13 20:03 ` Chris Mason
2009-10-13 20:55 ` Zach Brown
2009-10-12 20:50 ` Tomasz Chmielewski
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=87fx9jugp3.fsf@faran.nsc.liu.se \
--to=paran@lysator.liu.se \
--cc=athena@fftw.org \
--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