All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chet Hosey <chosey@nauticom.net>
To: reiserfs-list@namesys.com
Subject: Re: dmapi support for reiser4
Date: Thu, 30 Jun 2005 07:42:31 -0400	[thread overview]
Message-ID: <42C3DAA7.8040402@nauticom.net> (raw)
In-Reply-To: <20050630071249.GR31371@vestdata.no>

Ragnar Kjørstad wrote:

>On Wed, Jun 29, 2005 at 06:41:46PM -0400, Chet Hosey wrote:
>  
>
>>Is there a standard VFS interface that these filesystems present, or is
>>it done via filesystem-specific extensions? If the latter, perhaps you
>>should consider submitting a kernel patch that adds the required
>>interface to the VFS layer, and note in your submission that XFS and JFS
>>aren't compliant.
>>    
>>
>
>The OpenXDSM project intended to extend the VFS layer with a few extra
>functions and to implement a generic XDSM/DMAPI layer on top of that.
>
>The project never really got anywhere and the sourceforge webpage has
>been removed, but you can still find some pointers to the VFS
>discussions if you google for OpenXDSM.
>
>  
>
In short, no, there's no standard VFS implementation. Gotcha.

>In short, the filesystems needed to be extended with functionality in
>two primary areas:
>- persistent storage of metadata
>- beeing able to punch holes in existing files.
>
>The first item has since been solved by extended attributes, and I
>believe there were some ideas about how to change truncate to also be
>able to punch holes. There were probably a few more things needed to be
>done, but I don't remember. Google probably knows.
>  
>
So essentially you're looking for an interface by which you can produce
holes in files? That sounds like a minor feature request, certainly one
without which a filesystem might still be a "real competitor" in a
general market.

>>You said that "reiser4 will not be a real competitor without this". A
>>competitor in what market? Can you name an application that depends on
>>DMAPI and is so important that without that particular application
>>Reiser4 is not appropriate for storing files?
>>    
>>
>
>DMAPI is used for Hirarchial Storage Management, migrating unused files
>to slower medium such as tape. It can also be used by backupsystems.
>
>I should add though, that not everybody that does HSM are big fans of
>DMAPI. It's quite possible that it would be just as productive to add a
>_different_ API for HSM to linux as adding DMAPI.
>
>  
>
Let me clarify -- you made claims that reiser4 isn't a "real competitor"
without DMAPI. Specifically, DMAPI. I asked whether you can name a
DMAPI-dependent application which *must* work on a given filesystem in
order for it to be a "real competitor". You haven't thus far. Now you're
saying, well, not necessarily DMAPI, but *something*.You're being vague.

To publicly claim that Reiser4 isn't a "real competitor" without
your-favorite-buzzword without providing some *actual evidence* as to
why this is the case seems a little bit rude. Can you support your
accusations?

>>Just curious, as I'd not heard of DMAPI prior to your post, but you
>>claim it's quite important.
>>    
>>
>
>It is important in a relatively narrow (high end) market, not really for
>desktops and low end servers.
>
>  
>
Again, I'd consider it polite to either clarify or adjust your claims
that Reiser4 isn't a "real competitor" (note that you didn't initially
name *any* market, you just made a broad statement that Reiser4 can't
compete).

-- chet


  reply	other threads:[~2005-06-30 11:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28  9:34 dmapi support for reiser4 Bjoern JACKE
2005-06-28 11:31 ` Vladimir Saveliev
2005-06-29 11:57   ` Bjoern JACKE
2005-06-29 16:15     ` Vladimir Saveliev
2005-06-29 16:32       ` Bjoern JACKE
2005-06-29 22:41     ` Chet Hosey
2005-06-30  7:12       ` Ragnar Kjørstad
2005-06-30 11:42         ` Chet Hosey [this message]
2005-06-30  3:07     ` Hans Reiser

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=42C3DAA7.8040402@nauticom.net \
    --to=chosey@nauticom.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.