All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linda A. Walsh" <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Question about extended attributes...
Date: Thu, 31 Jul 2008 17:11:01 -0700	[thread overview]
Message-ID: <48925495.7040804@tlinx.org> (raw)

my man page says extended xfs attributes can have 256-byte names
with up to 64K of data.

Is there a limit on the number of extended attributes max data size or 
name size?

I.e. could I have 1000 attributes with 64K of data each?

Is there a strong reason why the file and data sizes were limited to 
256/64K?
Would they be hard to 'generalize' to max-path-segment-len/max-filelen?

Only reason I wonder is wondering what file systems besides apple's 
"HPFS"(?) and
MS's NTFS, that allow alternate data-streams of arbitrary length.  I'm 
not sure about
the maximums on HPFS and NTFS, but I haven't _read_ of any notable 
limits (I'm sure
there are some, but it _seems_ you can store alternate file versions in 
different data-streams
on NTFS, for example...  I.e. could use it as a revision system, 
theoretically -- to save
older versions of the file with the right software -- but with XFS, it 
wouldn't be so
general case with a 64K data limit -- wouldn't be a show-stopper if one 
could 'link'
multiple data-segments, but am just curious about the limitations (not 
that I'm planning
on implementing a version control system using data-forks...it was just 
an example! :-)).

linda

             reply	other threads:[~2008-08-01  0:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01  0:11 Linda A. Walsh [this message]
2008-08-01  6:55 ` Question about extended attributes Timothy Shimmin
2008-08-01 12:32   ` Dave Chinner
2008-08-04  5:13     ` Timothy Shimmin

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=48925495.7040804@tlinx.org \
    --to=xfs@tlinx.org \
    --cc=xfs@oss.sgi.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.