From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f54.google.com ([209.85.218.54]:33922 "EHLO mail-oi0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752902AbcICDm6 (ORCPT ); Fri, 2 Sep 2016 23:42:58 -0400 Received: by mail-oi0-f54.google.com with SMTP id m11so60944774oif.1 for ; Fri, 02 Sep 2016 20:41:30 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1472870869.8290.17.camel@gmail.com> References: <1471023419.16857.9.camel@gmail.com> <1472676550.8145.1.camel@gmail.com> <52290114-3b37-2de5-9c9f-ceda6dff955b@suse.com> <1472734635.3137.4.camel@gmail.com> <0778dff0-cb43-d279-adb2-0e314b61110d@gmail.com> <1472747695.3137.7.camel@gmail.com> <1472827395.3713.6.camel@gmail.com> <9dee919a-0e81-5ba7-ddc6-7dcdb3a6b873@suse.com> <1472829630.3713.8.camel@gmail.com> <506f2875-8cea-2d99-3664-52ee546adcfd@suse.com> <1472846181.13263.2.camel@gmail.com> <1472854386.9717.7.camel@gmail.com> <1472870869.8290.17.camel@gmail.com> From: Chris Murphy Date: Fri, 2 Sep 2016 21:41:28 -0600 Message-ID: Subject: Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space To: Ronan Arraes Jardim Chagas Cc: Chris Murphy , Jeff Mahoney , "Austin S. Hemmelgarn" , Wang Xiaoguang , Btrfs BTRFS , Qu Wenruo Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Fri, Sep 2, 2016 at 8:47 PM, Ronan Arraes Jardim Chagas wrote: > Hi guys! > > Em Sex, 2016-09-02 às 16:39 -0600, Chris Murphy escreveu: >> Worth a shot, considering the opensuse/SLE 4.4 kernel has a shittonne >> of backports. It seems unlikely to me opensuse intends to not support >> your hardware (skylake?) > > Actually it is a peripheral we use to program embedded systems here and > the (proprietary) driver requires kernel >= 4.6. I barely use it. I am > really thinking to transfer it to another machine just to be able to > change my kernel. I suggest removing the hardware, and the proprietary driver, and retest the system with the existing Tumbleweed 4.7.0 kernel; and if that still fails, then try the Leap 4.4 kernel. Proprietary kernels can do all kinds of crazy things they shouldn't so it's entirely possible that driver is a factor in the problem. -- Chris Murphy