All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaya Potter <spotter@cs.columbia.edu>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2's bmap output
Date: Fri Oct 14 10:48:55 2005	[thread overview]
Message-ID: <1129304929.8092.50.camel@localhost.localdomain> (raw)
In-Reply-To: <20051014061251.GE9943@ca-server1.us.oracle.com>

On Thu, 2005-10-13 at 23:12 -0700, Mark Fasheh wrote:
> Hi,
> 
> On Fri, Oct 14, 2005 at 01:33:35AM -0400, Shaya Potter wrote:
> > I'm guessing this is because of its use of extents, and probably means
> > I've screwed myself in trying to use bmap in this way.  Is that a
> > correct assumption?  Is there any other interface into OCFS2 to tell if
> > a block is a "blank" sparse area?
> Unfortunately, no. Since OCFS2 doesn't currently support sparse files, the
> "holes" created are actually allocated and filled with zeros. Once
> allocated, they'll look no different from other file data.

a related question then.  Is sparse file support not planned at all for
OCFS2, or just "not currently" supported.

thanks.

  parent reply	other threads:[~2005-10-14 10:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14  0:33 [Ocfs2-devel] ocfs2's bmap output Shaya Potter
2005-10-14  1:12 ` Mark Fasheh
2005-10-14  1:18   ` Shaya Potter
2005-10-14 10:48   ` Shaya Potter [this message]
2005-10-14 16:31     ` Sunil Mushran
2005-10-14  3:51 ` Joel Becker

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=1129304929.8092.50.camel@localhost.localdomain \
    --to=spotter@cs.columbia.edu \
    --cc=ocfs2-devel@oss.oracle.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.