public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Smit Shah <getsmit@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: XFS Preallocate using ALLOCSP
Date: Mon, 15 Jun 2009 22:34:23 -0500	[thread overview]
Message-ID: <4A3712BF.7030101@sandeen.net> (raw)
In-Reply-To: <24042506.post@talk.nabble.com>

Smit Shah wrote:
> Hi, 
> 
> I wanted to preallocate the file using the ALLOCSP so that the preallocated
> space is zeroed out. Hence i used the xfsctl but the problem is that i
> cannot execute  it as a non-root user.  So i tried using fallocate but when
> i saw the xfs implementation of kernel it uses the RESVP cmd and  since the
> unwritten flag is set i am assuming that the performance of writing to the
> preallocated space will suffer because of the metadata updates. So is there
> a way to preallocate using ALLOCSP as a non-root user or else i would be
> required to modify the kernel ??
> 
> TIA, 
> Smit 

ALLOCSP simply writes 0s to a file.... you may as well do it using posix
calls, as a normal user, I think.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2009-06-16  3:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  0:18 XFS Preallocate using ALLOCSP Smit Shah
2009-06-16  2:00 ` Smit Shah
2009-06-16  3:34 ` Eric Sandeen [this message]
2009-06-16  6:44   ` Smit Shah
2009-06-16  7:34     ` Smit Shah
2009-06-16 15:16     ` Eric Sandeen
2009-06-16 16:42       ` Felix Blyakher
2009-06-16 17:28         ` Smit Shah
2009-06-16 17:32           ` Eric Sandeen
2009-06-16 21:38             ` Smit Shah
2009-06-17  1:04               ` Michael Monnerie
2009-06-16 17:41           ` Felix Blyakher
2009-06-16 21:42             ` Smit Shah
2009-06-16 22:05               ` Eric Sandeen
2009-06-16 22:32                 ` Felix Blyakher
2009-06-16 22:19               ` Smit Shah
2009-06-16 22:26               ` Felix Blyakher

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=4A3712BF.7030101@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=getsmit@gmail.com \
    --cc=linux-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox