Linux NILFS development
 help / color / mirror / Atom feed
From: Allison Holloway <ahollowa-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Reading and writing a large file
Date: Mon, 08 Sep 2008 12:35:17 -0500	[thread overview]
Message-ID: <48C56255.7080807@cs.wisc.edu> (raw)

Hi,

I want to run a program in NILFS that performs lots of random and 
sequential reads and writes on a large file.  The program uses pread64 
and pwrite64 to do the file accesses; I'm accessing the data 32KB at a 
time, and I give the location as the logical offset within the file.  It 
works fine on my department's AFS file system, but I'm having 2 issues 
with NILFS:
1) pwrite64 will sometimes fail, and I haven't figured out what it 
correlates to.  I know sometimes it's because the disk has run out of 
room, but I'm not sure that that is always the cause.
2) Garbage collection/ cleanup.  After enough blocks of the file have 
been rewritten (possibly multiple times), I'll get a disk full error.  
Then, even if I've deleted all the files in my nilfs partition, I cannot 
create a new non-empty file.  Is there a way to speed up the garbage 
collection process, or better interleave it with the program so I don't 
get these "disk full" errors?

Any help or insight you could give would be greatly appreciated!

Thank you,
Allison

             reply	other threads:[~2008-09-08 17:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 17:35 Allison Holloway [this message]
     [not found] ` <48C56255.7080807-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
2008-09-09  6:00   ` Reading and writing a large file Ryusuke Konishi

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=48C56255.7080807@cs.wisc.edu \
    --to=ahollowa-hcno3ddehluvc3sceru5cw@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org \
    /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