public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Grozdan <neutrino8@gmail.com>
Cc: Brian Foster <bfoster@redhat.com>, "Frank ." <frank_1005@msn.com>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Delaylog information enquiry
Date: Thu, 31 Jul 2014 08:57:32 +1000	[thread overview]
Message-ID: <20140730225732.GQ20518@dastard> (raw)
In-Reply-To: <CAFLt3pjdwdSOxVhbTFemReyNr9HnUodA-NL5bND2yRJGX2GBuA@mail.gmail.com>

On Wed, Jul 30, 2014 at 11:18:11PM +0200, Grozdan wrote:
> I don't want to start another thread as this is my last question but
> it's one unrelated to the original question from Frank

You should always start a new thread when you have an unrelated
question. At minimum, you should change the subject line...

> One of my partitions was almost full (there was 5 GB over according to
> df -h). I had about 8 torrents open in the client, all sizes between 4
> and 6 GB (they were all downloaded and got never "released" from the
> client as I was seeding back). When I tried to add a torrent to
> download which was 3 GB, the client reported that there was no more
> space left over on the partition. I suspect this is related to
> speculative preallocation and because the 8 torrents were all "open"
> they still had extra space allocated by the speculative preallocation
> and thus I couldn't add the 3GB torrent even though df says there was
> 5GB over but in reality it was much less. Am I correct on this or is
> there something completely else that happened?

No idea - not enough information. Please start a new thread,
including the information here:

http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F

as well as the 'xfs_bmap -vp' output for the torrents in question.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

      reply	other threads:[~2014-07-30 22:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29  8:53 Delaylog information enquiry Frank .
2014-07-29 12:38 ` Brian Foster
2014-07-29 23:41   ` Dave Chinner
2014-07-30  5:42     ` Grozdan
2014-07-30  8:18       ` Dave Chinner
2014-07-30 11:44         ` Frank .
2014-07-30 22:53           ` Dave Chinner
2014-07-30 21:18         ` Grozdan
2014-07-30 22:57           ` Dave Chinner [this message]

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=20140730225732.GQ20518@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=frank_1005@msn.com \
    --cc=neutrino8@gmail.com \
    --cc=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