linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor M <igork20@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: No space left on device, problem
Date: Sat, 26 Oct 2013 23:00:28 +0200	[thread overview]
Message-ID: <CAEezp7s=44iMfmhxsOoeukex9BABU_5CvmWuU_Ha_vyZRAefcw@mail.gmail.com> (raw)
In-Reply-To: <CAEezp7tJ3eouogd2zuDuLVnAhHk8VPi7ytFNQ1Rh51vfioVzHg@mail.gmail.com>

Some more info, exact error message is:

cp: writing ‘/usr/local/mysql/data/gbdata/parts_0015.MYI’: No space
left on device
cp: failed to extend ‘/usr/local/mysql/data/gbdata/parts_0015.MYI’: No
space left on device

Files are 2.7G - 7.7G big.

On Sat, Oct 26, 2013 at 9:46 PM, Igor M <igork20@gmail.com> wrote:
> Hello,
>
> I just upgraded kernel to 3.11.6 added new disk and created btrfs:
>
> # mkfs.btrfs /dev/sdb
> # mount -t btrfs -o compress=lzo,compress-force=lzo /dev/sdb
> /usr/local/mysql/data
>
> I started copying files from old disk and then I got 'No space left on
> device', but there is a lot of space.
>
> # df -h
> Filesystem                Size  Used Avail Use% Mounted on
> /dev/sdb                  2.8T  110G  2.7T   4% /usr/local/mysql/data
>
> # btrfs fi show
> Label: none  uuid: c0bfcb22-8b7c-4936-afcd-7acdf58f1d6c
>         Total devices 1 FS bytes used 108.68GB
>         devid    1 size 2.73TB used 113.04GB path /dev/sdb
>
> # btrfs fi df /usr/local/mysql/data
> Data: total=111.01GB, used=108.25GB
> System, DUP: total=8.00MB, used=20.00KB
> System: total=4.00MB, used=0.00
> Metadata, DUP: total=1.00GB, used=441.91MB
> Metadata: total=8.00MB, used=0.00
>
> I tried balance from FAQ:
>
> # btrfs fi balance start -dusage=5 /usr/local/mysql/data
> Done, had to relocate 4 out of 117 chunks
>
>
> But it doesn't help. When I try to copy file there is still 'No space
> left on device'.
>
> What to do ?
>
>
> Regards,
>
> Igor

  reply	other threads:[~2013-10-26 21:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-26 19:46 No space left on device, problem Igor M
2013-10-26 21:00 ` Igor M [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2013-10-27  1:00 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
2013-10-28 19:15     ` 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='CAEezp7s=44iMfmhxsOoeukex9BABU_5CvmWuU_Ha_vyZRAefcw@mail.gmail.com' \
    --to=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).