linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <tch@virtall.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	igork20@gmail.com
Subject: Re: No space left on device, problem
Date: Sun, 27 Oct 2013 10:00:22 +0900	[thread overview]
Message-ID: <20131027100022.4c76e1e7@virtall.com> (raw)

> 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.


-- 
Tomasz Chmielewski
http://wpkg.org

             reply	other threads:[~2013-10-27  1:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-27  1:00 Tomasz Chmielewski [this message]
2013-10-27  8:50 ` No space left on device, problem 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
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=20131027100022.4c76e1e7@virtall.com \
    --to=tch@virtall.com \
    --cc=igork20@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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).