From: Theodore Tso <tytso@mit.edu>
To: Felipe Franciosi <ozzy@doc.ic.ac.uk>
Cc: Andreas Dilger <adilger@sun.com>, linux-ext4@vger.kernel.org
Subject: Re: Simple inode question (ext2/3)
Date: Wed, 25 Feb 2009 09:38:21 -0500 [thread overview]
Message-ID: <20090225143821.GH7064@mit.edu> (raw)
In-Reply-To: <417E5333-32B8-42AA-A498-011DF1DDB074@doc.ic.ac.uk>
On Wed, Feb 25, 2009 at 10:59:22AM +0000, Felipe Franciosi wrote:
> As a matter of fact, I didn't see any critics to the question below. I
> can only assume that messing with inodes can look academic or not
> depending on the phase of the moon or something.
>
> On 6 Jan 2009, at 10:36, Rohit Sharma wrote:
>> I want to read data blocks from one inode
>> and copy it to other inode.
>>
>> I mean to copy data from data blocks associated with one inode
>> to the data blocks associated with other inode.
>>
>> Is that possible in kernel space.?
>> --
Actually, I asked Rohit what they were doing back September, 2008.
http://article.gmane.org/gmane.comp.file-systems.ext4/9142
Personally, I'm not really convinced by the approach which the fscops
project is adopting, but that's up to them to figure out. I was
amused though by their powerpoint slides which claim that they are "on
the way to being accepted in the mainline kernel" --- that seems a
little gradious, given that they haven't even submitted any code for
review yet.
- Ted
next prev parent reply other threads:[~2009-02-25 14:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 17:13 Simple inode question (ext2/3) Felipe Franciosi
2009-02-24 18:12 ` Felipe Franciosi
2009-02-24 19:07 ` Theodore Tso
2009-02-24 19:32 ` Felipe Franciosi
2009-02-24 21:05 ` Theodore Tso
2009-02-24 21:48 ` Felipe Franciosi
2009-02-25 4:06 ` Andreas Dilger
2009-02-25 10:59 ` Felipe Franciosi
2009-02-25 13:11 ` Theodore Tso
2009-02-25 14:10 ` Greg Freemyer
2009-02-25 14:38 ` Theodore Tso [this message]
2009-03-28 7:57 ` SandeepKsinha
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=20090225143821.GH7064@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ozzy@doc.ic.ac.uk \
/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).