BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi guys, I'm facing a daily problem with BTRFS. Almost everyday, I get the message "No space left on device". Sometimes I can recover by balancing the system but sometimes even balancing does not work due to the lack of space. In this case, only a hard reset works if I can't delete some files.

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Em Sex, 2016-08-12 às 12:02 -0600, Chris Murphy escreveu: > Tons of unallocated space. What kernel messages do you get for the > enospc? It sounds like this will be one of the mystery -28 error file > systems. So far as I recall the only work around is recreating the > file system. There are two

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Em Seg, 2016-08-15 às 17:24 -0600, Chris Murphy escreveu: > On Mon, Aug 15, 2016 at 5:12 PM, Ronan Chagas > wrote: > > > > Hi guys! > > > > It happened again. The computer was completely unusable. The only > > useful > > message I saw was this one: > > > >

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

New information guys! I formatted using the latest Tumbleweed snapshot (btrfs-progs v4.7+20160729) and I still have the same problem. I notice two things. First, when I see the "No space left on device", it is fixed when the Metadata space increases **a lot**. For example, when the error first

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

The same thing just happened again! And now it was also fixed automatically, but now I have: Metadata,DUP: Size:33.50GiB, Used:812.78MiB -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi guys! And the problem happened again. This time, I was only using Mozilla Firefox. I could get the very first message after the error. I hope it brings more information: [28039.672199] [ cut here ] [28039.672253] WARNING: CPU: 3 PID: 31800 at ../fs/btrfs/qgroup.c:2667

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi Jeff, Em Sex, 2016-09-02 às 10:26 -0400, Jeff Mahoney escreveu: > I explained what I think Ronan's issue is in another part of the > thread > just now.  I don't think that's a severe issue at > all.  Annoying?  Sure, > but I'm more concerned with the underlying ENOSPC issue.  Without > more >

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi Jeff, Em Sex, 2016-09-02 às 10:48 -0400, Jeff Mahoney escreveu: > Sorry, I miscommunicated there.  The WARN_ON is annoying.  It's the > underlying issue that's causing you to lose work that is the one that > concerns me. >  Oh, OK, I see, sorry about that :) Thus, if disabling quotas does

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi guys! Jeff was right. I had the problem again today and quotas are disabled now. I couldn't get any useful message in log this time. Look at the metadata: btrfs fi usage / Overall: Device size:   1.26TiB Device allocated:   43.07GiB Device unallocated:

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi again guys! After I rebooted the computer, I still can't run balance on metatada: btrfs balance start -musage=1 / ERROR: error during balancing '/': No space left on device There may be more info in syslog - try dmesg | tail dmesg shows: [ 2022.530285] BTRFS info (device sda6): relocating

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi! Em Sex, 2016-09-02 às 15:34 -0600, Chris Murphy escreveu: > Except for your software build case, I have about the same workload > you have with two machines, one SSD one HDD, using 4.7.0 for a month, > and then 4.7.2 for the last week. I haven't had any enospc on these > two systems. > > I

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

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

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi Chris, Em Sex, 2016-09-02 às 21:41 -0600, Chris Murphy escreveu: > 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

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi Jeff, Em Qui, 2016-09-01 às 13:43 -0400, Jeff Mahoney escreveu: > Absolutely.  It doesn't affect the ability to take, retain, or > recover > using snapshots.  It only affects the ability to see how much space a > particular snapshot is using on disk, both from the user wanting to > know > and

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi Jeff, Em Qui, 2016-09-01 às 13:12 -0400, Jeff Mahoney escreveu: > It's not.  We use qgroups because that's the only way we can track > how > much space each subvolume is using, regardless of whether anyone > wants > to do enforcement.  When it's working properly, snapper can make use > of >

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi! Em Qua, 2016-08-31 às 17:09 -0600, Chris Murphy escreveu: > OK so Ronan, I'm gonna guess the simplest work around for your > problem > is to disable quota support, and see if the problem happens again. > Look at the output of the command proposed by Jeff: btrfs qgroup show / qgroupid   

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Em Ter, 2016-08-30 às 10:44 -0600, Chris Murphy escreveu: > It sounds related to read-only snapshots to me. I wonder if this > system has something busy that's writing to a file, database, even > maybe something just spamming journald, and then there's a read-only > snapshot during the write,

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Em Qui, 2016-09-01 às 09:21 -0400, Austin S. Hemmelgarn escreveu: > Yes, you can just run `btrfs quota disable /` and it should > work.  This  > ironically reiterates that one of the bigger problems with BTRFS is > that  > distros are enabling unstable and known broken features by default > on  >

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi! Em Ter, 2016-08-30 às 10:12 +0800, Wang Xiaoguang escreveu: > For metadata, "bytes_may_use" is about 80GB, it's very big, > I think this value is very abnormal. > > So this explains why you have huge unallocated space, you still > get ENOSPC error. In kernel btrfs, there is a function >

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi all! Em Seg, 2016-09-05 às 16:49 +0800, Qu Wenruo escreveu: > Just like what Wang has mentioned, would you please paste all the > output  > of the contents of /sys/fs/btrfs//allocation? > > It's recommended to use "grep . -IR " to get all the data as > it  > will show the file name. So, one

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi Josef, Em Ter, 2016-09-13 às 17:01 -0400, Josef Bacik escreveu: > I just started paying attention to this, the last kernel I saw you > were running  > was 4.7.  Have you tried a recent kernel, like chris's tree? > > > git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git >

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi Chris, Em Qua, 2016-09-14 às 16:25 -0600, Chris Murphy escreveu: > All I can think of is the file system has gotten into a unique state > through a combination of events. I'm still suspicious that qgroups is > contributing to the problem even after being disabled. The workload > you're talking

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi guys, One more time I saw the problem. It begins to happen on a daily basis now. Unfortunately the `enospc_debug` flag did not help. I did not see any new information in the logs. This time, only a hard reset worked. I could not even reboot using gnome panel. Best regards, Ronan Arraes -- To

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi! Em Ter, 2016-09-13 às 11:17 +0800, Wang Xiaoguang escreveu: > It maybe a irrelevant question, but do you have compression enabled? > > Regards, > Xiaoguang Wang No, I do not have compression enabled. I'm using openSUSE's default configuration. By the way, I was wrongly mounting the

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi guys, I just have the problem again. Now, it happens during the lunch time when the machine was idle. Only the system processes were running. It was not the first time that I saw this problem just after lunch when the machine stayed idle for a long period (+- 1h).  Here is the information

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Em Seg, 2016-08-22 às 14:49 -0600, Chris Murphy escreveu: > This is really weird. I'm running 4.7.0 (Fedora) and I'm not > experiencing problems, let alone this. What is this kernel's > provenance? Is it a plain mainline 4.7.0 that you built? I'm not > really sure what to recommend except maybe

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi! Em Seg, 2016-08-29 às 20:12 +0800, Wang Xiaoguang escreveu: > When strange ENOSPC errors occur, I think "btrfs fi usage" > or "btrfs di df" do not help too much. Their output do not > reflect btrfs kernel current status :) > > Would you please provide attribute files' values in  >