From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dkim2.fusionio.com ([66.114.96.54]:60789 "EHLO dkim2.fusionio.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755559Ab3J1TFk (ORCPT ); Mon, 28 Oct 2013 15:05:40 -0400 Received: from mx1.fusionio.com (unknown [10.101.1.160]) by dkim2.fusionio.com (Postfix) with ESMTP id 610AC9A0356 for ; Mon, 28 Oct 2013 13:05:40 -0600 (MDT) Date: Mon, 28 Oct 2013 15:05:38 -0400 From: Josef Bacik To: Igor M CC: Tomasz Chmielewski , "linux-btrfs@vger.kernel.org" Subject: Re: No space left on device, problem Message-ID: <20131028190538.GF4543@localhost.localdomain> References: <20131027100022.4c76e1e7@virtall.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" In-Reply-To: Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Sun, Oct 27, 2013 at 09:50:37AM +0100, Igor M wrote: > On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski wrote: > >> Still no messages. Parameter seems to be active as > >> /sys/module/printk/parameters/ignore_loglevel is Y, but there are no > >> messages in log files or dmesg. Maybe I need to turn on some kernel > >> debugging option and recompile kernel ? > >> Also I should mention that cca 230G+ data was copied before this error > >> started to occur. > > > > I think I saw a similar issue before. > > > > Can you try using rsync with "--bwlimit XY" option to copy the files? > > > > The option will limit the speed, in kB, at which the file is being > > copied; it will work even when source and destination files are on a > > local machine. > > > > Also I run strace cp -a .. > ... > read(3, "350348f07$0$24520$c3e8da3$fb4835"..., 65536) = 65536 > write(4, "350348f07$0$24520$c3e8da3$fb4835"..., 65536) = 65536 > read(3, "62.76C52BF412E849CB86D4FF3898B94"..., 65536) = 65536 > write(4, "62.76C52BF412E849CB86D4FF3898B94"..., 65536) = -1 ENOSPC (No > space left on device) > > Last two write calls take a lot more time, and then last one returns > ENOSPC. But if this write is retryed, then it succeeds. > I tried with midnight commander and when error occurs, if I Retry > operation then it finishes copying this file until error occurs again > at next file. > > With --bwlimit it seems to be better, lower the speed later the error > occurs, and if it's slow enough copy is successfull. > But now I'm not sure anymore. I copied a few files with bwlimit, and > now sudenly error doesn't occur anymore, even with no bwlimit. > I'll do some more tests. I just sent a patch to the list [PATCH] Btrfs: make sure the delalloc workers actually flush compressed writes Can you run this patch and see if it makes a difference for your test? Thanks, Josef