From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Marc MERLIN <marc@merlins.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Scrub: no spae left on device
Date: Tue, 8 Dec 2015 11:00:50 -0500 [thread overview]
Message-ID: <5666FEB2.9060905@gmail.com> (raw)
In-Reply-To: <20151208150638.GL27889@merlins.org>
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
On 2015-12-08 10:06, Marc MERLIN wrote:
> Howdy,
>
> Why would scrub need space and why would it cancel if there isn't enough of
> it?
> (kernel 4.3)
>
Wild guess here, but maybe scrub unconditionally updates the error
counters, regardless of whether any errors were found or not?
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
prev parent reply other threads:[~2015-12-08 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 15:06 Scrub: no spae left on device Marc MERLIN
2015-12-08 15:37 ` Holger Hoffstätte
2015-12-08 15:46 ` Lionel Bouton
2015-12-08 16:02 ` Holger Hoffstätte
2015-12-08 16:06 ` Marc MERLIN
2015-12-08 16:24 ` Holger Hoffstätte
2015-12-08 16:39 ` Marc MERLIN
2015-12-09 6:46 ` Duncan
2015-12-08 15:39 ` Lionel Bouton
2015-12-08 16:00 ` Austin S Hemmelgarn [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=5666FEB2.9060905@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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