All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Richard Scobie <richard@sauce.co.nz>
Cc: xfs@oss.sgi.com
Subject: Re: Filestreams
Date: Sun, 08 Jun 2008 22:31:49 -0500	[thread overview]
Message-ID: <484CA425.3080606@sandeen.net> (raw)
In-Reply-To: <484B15A3.4030505@sauce.co.nz>

Richard Scobie wrote:
> Is my understanding of filestreams correct, in that files written to a 
> particular filestreams enabled directory are all allocated to 1 ag as 
> long as the filestreams timeout is not exceeded - which I believe is 30s?
> 
> In other words, if I copy 100 files into a directory, (cp -a 
> dir_containing_100_files dest_dir), wait 60 seconds and do (cp -a 
> dir_containing_100_different_files dest_dir), each directory and 
> contents in dest_dir will be stored in a single, different ag?
> 
> Also, would it be possible for the filestreams parameter to be added to 
> man pages/kernel docs?

Yes please :)  I was just noticing last week that there is no
documentation anywhere on this feature ....

-Eric

> Thanks,
> 
> Richard
> 
> 

  reply	other threads:[~2008-06-09  3:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-07 23:11 Filestreams Richard Scobie
2008-06-09  3:31 ` Eric Sandeen [this message]
2008-06-10  1:49   ` Filestreams Timothy Shimmin
2008-06-10  2:14     ` Filestreams Richard Scobie
2008-06-10 23:09     ` Filestreams (and 64bit inodes) Richard Scobie
2008-06-11  1:39       ` Timothy Shimmin
2008-06-11  2:47         ` Richard Scobie
2008-06-11  3:23         ` Eric Sandeen
2008-06-12 13:52           ` Eric Sandeen
2008-06-13  1:28             ` Greg Banks
2008-06-13  3:06               ` Eric Sandeen
2008-06-13  3:24                 ` Greg Banks
2008-06-13  3:20               ` Mark Goodwin
2008-06-13  3:40                 ` Greg Banks
2008-06-13  3:46                   ` Eric Sandeen
2008-06-13  3:57                     ` Greg Banks
2008-06-13  5:35                   ` Greg Banks
2008-06-13 13:28                     ` Eric Sandeen
2008-06-13  3:45                 ` Eric Sandeen

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=484CA425.3080606@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=richard@sauce.co.nz \
    --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.