From patchwork Fri Dec 18 20:38:04 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Christoph Biedl X-Patchwork-Id: 7887801 Return-Path: X-Original-To: patchwork-linux-btrfs@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.136]) by patchwork2.web.kernel.org (Postfix) with ESMTP id 1B038BEEE5 for ; Fri, 18 Dec 2015 20:38:16 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id ECA1B204D2 for ; Fri, 18 Dec 2015 20:38:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B31B62051C for ; Fri, 18 Dec 2015 20:38:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965182AbbLRUiJ (ORCPT ); Fri, 18 Dec 2015 15:38:09 -0500 Received: from manchmal.in-ulm.de ([217.10.9.201]:57074 "EHLO manchmal.in-ulm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964992AbbLRUiH (ORCPT ); Fri, 18 Dec 2015 15:38:07 -0500 Date: Fri, 18 Dec 2015 21:38:04 +0100 From: Christoph Biedl To: linux-btrfs Subject: Re: ERROR: scrubbing failed for device id 1: ret=-1, errno=28 (No space left on device) Message-ID: <1450469988@msgid.manchmal.in-ulm.de> References: <1450423394@msgid.manchmal.in-ulm.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_HI, T_RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Henk Slager wrote... > you need to do some balancing, as I think that the free space is too > fragmented and the system fails to allocate extra metadata space > needed for scrub doing writes into metadata. > > # btrfs balance start -dusage= > with number somewhere between 5 and 50; first start with lower number > and repeat and increase until the 5.17GiB gets closer down to the > 3.75GiB Thanks, that one worked with number 100. Still some ENOSPC errors but appeareantly good enough to make scrubbing work. > The issue is that for for a filesystem of this size (6.5GiB), it would > have been better to have mixed data/metadata allocation. See help of > mkfs.btrfs. So maybe you want to recreate the fs like that, otherwise > you might easily hit this problem again if you don't monitor free > space / balance regularly. Will keep that in mind. Just out of curiousity: Initially, the file system size was just 4 Gibyte. Is it possible this made things worse? Oh, and by the way: Christoph --- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html --- a/Documentation/mkfs.btrfs.asciidoc +++ b/Documentation/mkfs.btrfs.asciidoc @@ -77,7 +77,7 @@ where the space is reserved for the other block group type, is not available for allocation and can lead to ENOSPC state. + The recommended size for the mixed mode is for filesystems less than 1GiB. The -soft recommendation is to use it for filesystems smaller than 5GiB. Thie mixed +soft recommendation is to use it for filesystems smaller than 5GiB. The mixed mode may lead to degraded performance on larger filesystems, but is otherwise usable, even on multiple devices. +