All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Anders Widman <andewid@tnonline.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Multiple data streams...
Date: Wed, 02 Apr 2003 11:12:29 -0500	[thread overview]
Message-ID: <3E8B0BED.2070004@suse.com> (raw)
In-Reply-To: <6167696812.20030402112847@tnonline.net>

[-- Attachment #1: Type: text/plain, Size: 2038 bytes --]

Anders Widman wrote:
>    Is this supported, or will it be supported by ReiserFS?
>    I  use  this  feature quite quite much.. Maybe this is something to
>    add to ReiserFS?
> 
>    There is very brief info at Microsoft's website:
> 
>    http://www.microsoft.com/windows2000/techinfo/reskit/en-us/core/fncc_fil_khzt.asp

	I have an implementation of extended attributes that has been included 
in the SuSE kernel for some time now. It's not at all suitable for 
filestreams with a lot of data, as the Linux extended attribute 
interface requires that the entire attribute be read and written in one 
chunk. However, for small things, such as mime type, email sender, and 
perhaps even small thumbprints, this wouldn't be a problem. The sizes of 
xattrs in my implementation aren't limited in size, as they are 
implemented as regular files in a hidden tree. [*]

	The patches are against the SuSE kernel at the moment, but if there's 
enough interest, I could split them out to depend on the generic  ACL/EA 
patches from Andreas Gruenbacher and Chris Mason's data logging and 
quota patches.

	I suppose that since the xattr files are normal files, it would be 
pretty easy to implement a "datastream" xattr that could be accessed 
using normal tools. The semantics could be similar to the windows 
implementation, e.g. /foo/bar/file:datastream1 (Lookup the file verbatim 
first, then try datastreams) However, since most of the userspace tools 
are unaware of xattrs, the same restrictions that apply for any other 
xattr apply: they'll be lost if you copy/backup with tools that don't 
know about them.

	-Jeff

[*] My design requirements included not forking the filesystem in an 
incompatible manner, this was the best way I came up with. If a 
filesystem with xattrs on it is mounted with them disabled or by a 
kernel that doesn't support them, the xattrs appear in a tree owned by 
root (mode 700), with all the files owned by the user owning the file 
that the xattr is associated with.

-- 
jeffm@suse.com
jeffm@csh.rit.edu

[-- Attachment #2: Type: application/pgp-signature, Size: 252 bytes --]

  parent reply	other threads:[~2003-04-02 16:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02  9:28 Multiple data streams Anders Widman
2003-04-02  9:47 ` Anders Widman
2003-04-02 16:43   ` Hans Reiser
2003-04-03 16:49   ` Valdis.Kletnieks
2003-04-02 12:40 ` Russell Coker
2003-04-02 13:08   ` Anders Widman
2003-04-02 21:32     ` Russell Coker
2003-04-03 19:00       ` Hans Reiser
2003-04-03 19:57         ` Russell Coker
2003-04-03 21:53           ` Hans Reiser
2003-04-02 15:18   ` Oleg Drokin
2003-04-02 15:30   ` Alexander G. M. Smith
2003-04-02 16:12 ` Jeff Mahoney [this message]
2003-04-02 16:53   ` Hans Reiser
2003-04-02 17:07     ` Chris Mason
2003-04-02 17:13       ` Nikita Danilov
2003-04-03 18:37         ` Hans Reiser
2003-04-03 19:02           ` Chris Mason
2003-04-03 19:50             ` Hans Reiser
2003-04-03 20:09               ` Chris Mason
2003-04-04  7:41           ` Nikita Danilov

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=3E8B0BED.2070004@suse.com \
    --to=jeffm@suse.com \
    --cc=andewid@tnonline.net \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.