linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Lorenzo Allegrucci <l.allegrucci@tiscali.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext2/3 fragments support
Date: Thu, 10 Apr 2003 14:04:00 -0600	[thread overview]
Message-ID: <20030410140400.G26054@schatzie.adilger.int> (raw)
In-Reply-To: <200304102135.19381.l.allegrucci@tiscali.it>; from l.allegrucci@tiscali.it on Thu, Apr 10, 2003 at 09:35:19PM +0000

On Apr 10, 2003  21:35 +0000, Lorenzo Allegrucci wrote:
> Fragments support on ext2/3 filesystems seems disabled
> or non fully functional.
> Are there any plans to implement fragments?

They have never been enabled.  The "goal" is to imlement fragments as a
type of extended attribute, so that they can be packed into a single block
or inline in a larger inode (along with other EA data) instead of being
fixed-size hunks.

The first thing that needs doing is fixing the current ext2/3 EA sharing
scheme, which currently only shares blocks if they are identical and is
therefore only really useful for ACLs.

The best proposal so far for EA sharing is to put them into a directory-like
structure (maybe one dir per block group or something) and have the EA type
and data be packed inline into the directory (like the inode number and
filename are done with regular directories).  Each inode would also have a
"catalog" of the EAs that it has (itself an EA, either inline in a larger
inode or in the directory pointed to by, say, i_faddr).  Shared entries would
be like hard links pointed to by mutliple catalogs, with a refcount.

This was discussed on ext2-devel about a year ago, but no takers on the
implementation yet (I might eventually need to implement it this year if
nobody beats me to it, because we need better EAs than one per 4kB of disk).

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2003-04-10 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-10 21:35 ext2/3 fragments support Lorenzo Allegrucci
2003-04-10 20:04 ` Andreas Dilger [this message]
2003-04-10 20:08 ` Maciej Soltysiak

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=20030410140400.G26054@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=l.allegrucci@tiscali.it \
    --cc=linux-kernel@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).