linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alin Dobre <alin.dobre@elastichosts.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: Negative qgroup sizes
Date: Fri, 02 May 2014 10:17:45 +0100	[thread overview]
Message-ID: <536362B9.7020505@elastichosts.com> (raw)
In-Reply-To: <pan$cea24$895c4bc2$f096e7bb$50b7a75d@cox.net>

Thanks for the response, Duncan.

On 01/05/14 17:58, Duncan wrote:
> 
> Tho you are slightly outdated on your btrfs-progs version, 3.14.1 being 
> current.  But I think the code in question is kernel code and the progs 
> simply report it, so I don't think that can be the problem in this case.

Yes, I'm aware that 3.14 version of btrfs progs was already there, but
this is just for couple of weeks and I'm pretty sure that the kernel
code (which does the real time accounting) is broken.

> So if you are doing snapshots, you can try not doing them (switching to 
> conventional backup if necessary) and see if that stabilizes your 
> numbers.  If so, you know there's still more problems in that area.
> 
> Of course if the subvolumes involved aren't snapshotted, then the problem 
> must be elsewhere, but I do know the snapshotting case /is/ reasonably 
> difficult to get right... while staying within a reasonable performance 
> envelope at least.
> 

I have already searched and found some patches around this issue, but I
thought I'd also mention the issue on this mailing list and hoped that I
somehow missed something. The subvolumes are highly probable to be
snapshotted, so this might indeed be the case.

Cheers,
Alin.

      reply	other threads:[~2014-05-02  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-01 13:32 Negative qgroup sizes Alin Dobre
2014-05-01 16:58 ` Duncan
2014-05-02  9:17   ` Alin Dobre [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=536362B9.7020505@elastichosts.com \
    --to=alin.dobre@elastichosts.com \
    --cc=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).