From: Josef Bacik <jbacik@fusionio.com>
To: Igor M <igork20@gmail.com>
Cc: Tomasz Chmielewski <tch@virtall.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: No space left on device, problem
Date: Mon, 28 Oct 2013 15:05:38 -0400 [thread overview]
Message-ID: <20131028190538.GF4543@localhost.localdomain> (raw)
In-Reply-To: <CAEezp7u4-iYN01oXcoodzqsy8_nJPYWL-i0rjFsOc=3C0eSz-g@mail.gmail.com>
On Sun, Oct 27, 2013 at 09:50:37AM +0100, Igor M wrote:
> On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski <tch@virtall.com> 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
next prev parent reply other threads:[~2013-10-28 19:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 1:00 No space left on device, problem Tomasz Chmielewski
2013-10-27 8:50 ` Igor M
2013-10-27 8:56 ` Brendan Hide
2013-10-27 9:18 ` Igor M
2013-10-27 21:53 ` Igor M
2013-10-27 22:46 ` Chris Murphy
2013-10-27 23:27 ` Chris Murphy
2013-10-28 7:40 ` Igor M
2013-10-28 17:57 ` Chris Murphy
2013-10-28 19:07 ` Igor M
2013-10-28 19:05 ` Josef Bacik [this message]
2013-10-28 19:15 ` Igor M
-- strict thread matches above, loose matches on Subject: below --
2013-10-26 19:46 Igor M
2013-10-26 21:00 ` Igor M
2013-10-26 21:35 ` Chris Murphy
2013-10-26 21:53 ` Igor M
2013-10-26 22:17 ` Chris Murphy
2013-10-26 22:22 ` Igor M
2013-10-26 22:50 ` Igor M
2013-10-26 22:54 ` Igor M
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=20131028190538.GF4543@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=igork20@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tch@virtall.com \
/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;
as well as URLs for NNTP newsgroup(s).