From: David Nicol <davidnicol@gmail.com>
To: James Cloos <cloos@jhcloos.com>
Cc: linux-btrfs@vger.kernel.org, John Fremlin <john@fremlin.org>
Subject: Re: BTRFS should increase the hard-link in the same directory limit
Date: Tue, 23 Aug 2011 10:29:55 -0500 [thread overview]
Message-ID: <CAFwScO95=r8UUzmKRY-umKXBFP-PyPt9oafqMAxqEBR12vAL1w@mail.gmail.com> (raw)
In-Reply-To: <m3bovio1wp.fsf@jhcloos.com>
so there are these hundreds of message files, and when one is read, a
new link to The Markfile appears with a similar name as the read file?
Is that right?
if the point is to save inodes by making a directory entry that's a
hardlink to something already existing, why not link to the message
file?
On Sun, Aug 21, 2011 at 5:05 PM, James Cloos <cloos@jhcloos.com> wrote:
>>>>>> "JF" =3D=3D John Fremlin <john@fremlin.org> writes:
>
> JF> instead of creating a separate inode for each marked message, use=
s a
> JF> hardlink to a single markfile. This means that there maybe thousa=
nds
> JF> of hardlinks to the same inode in a single directory.
>
> And that behaviour is not limited to gnus. =C2=A0Many workflows use t=
hat idiom.
>
> -JimC
> --
> James Cloos <cloos@jhcloos.com> =C2=A0 =C2=A0 =C2=A0 =C2=A0 OpenPGP: =
1024D/ED7DAEA6
> --
> 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
>
--=20
"The tools expect that they have full, unlimited control of the hardwar=
e."
=C2=A0-- Intel Corporation
--
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:[~2011-08-23 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 15:13 BTRFS should increase the hard-link in the same directory limit John Fremlin
2011-08-21 22:05 ` James Cloos
2011-08-23 15:29 ` David Nicol [this message]
2011-08-22 14:54 ` Josef Bacik
2011-08-22 16:05 ` John Fremlin
2011-08-22 16:06 ` Josef Bacik
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='CAFwScO95=r8UUzmKRY-umKXBFP-PyPt9oafqMAxqEBR12vAL1w@mail.gmail.com' \
--to=davidnicol@gmail.com \
--cc=cloos@jhcloos.com \
--cc=john@fremlin.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;
as well as URLs for NNTP newsgroup(s).