Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: Chris Mason <clmason@fusionio.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: No space left on device (28)
Date: Fri, 22 Mar 2013 12:13:56 +0600	[thread overview]
Message-ID: <20130322121356.237e57e8@natsu> (raw)
In-Reply-To: <514B62A4.1030201@profihost.ag>

[-- Attachment #1: Type: text/plain, Size: 2529 bytes --]

On Thu, 21 Mar 2013 20:42:28 +0100
Stefan Priebe <s.priebe@profihost.ag> wrote:

I might be wrong here, but doesn't this

> rsync: rename 
> "/mnt/.software/kernel/linux-3.9-rc3/drivers/infiniband/hw/amso1100/.c2_ae.h.WEhLGP" 
> -> 
> ".software/kernel/linux-3.9-rc3/drivers/infiniband/hw/amso1100/c2_ae.h": 

...try to move a file from 

  "/mnt/.software/"

to

  ".software/"

(relative to current dir)??

Maybe you end up trying to rsync your array to a small root partition or
something?

> No space left on device (28)
> 
> # btrfs filesystem df /mnt/
> Data: total=18.14TB, used=15.05TB
> System, DUP: total=8.00MB, used=1.94MB
> System: total=4.00MB, used=0.00
> Metadata, DUP: total=23.98GB, used=17.98GB
> Metadata: total=8.00MB, used=0.00
> 
> Stefan
> 
> Am 21.03.2013 20:02, schrieb Chris Mason:
> > Quoting Stefan Priebe - Profihost AG (2013-03-21 14:35:59)
> >> Hi Chris,
> >>
> >> Am 21.03.2013 um 19:00 schrieb Chris Mason <chris.mason@fusionio.com>:
> >>
> >>> Quoting Stefan Priebe - Profihost AG (2013-03-21 04:03:04)
> >>>> Hi,
> >>>>
> >>>> while copying a 15GB file to my btrfs volume i'm getting "No space left
> >>>> on device".
> >>>>
> >>>> Some information:
> >>>>
> >>>> # btrfs filesystem df /mnt/
> >>>> Data: total=18.14TB, used=15.05TB
> >>>> System, DUP: total=8.00MB, used=1.94MB
> >>>> System: total=4.00MB, used=0.00
> >>>> Metadata, DUP: total=23.98GB, used=17.97GB
> >>>> Metadata: total=8.00MB, used=0.00
> >>>>
> >>>> # df -h
> >>>> Filesystem             Size  Used Avail Use% Mounted on
> >>>> /dev/mapper/raid54tb1   19T   16T  3,1T  84% /mnt
> >>>>
> >>>> # btrfs fi show
> >>>> Label: none  uuid: fc23c4a8-a351-4c91-96a2-ee6abeffe59a
> >>>>         Total devices 1 FS bytes used 15.07TB
> >>>>         devid    1 size 18.19TB used 18.19TB path /dev/dm-3
> >>>>
> >>>> # btrfs fi balance start -dusage=5 /mnt/
> >>>> Done, had to relocate 0 out of 18604 chunks
> >>>>
> >>>> What wrong here? What is about the last 3TB?
> >>>
> >>> Which kernel are you running?
> >>>
> >>> -chris
> >>
> >> vanilla 3.8.3.
> >
> > Ok, with the 3.9 merge window Josef changed how we do the reservations.
> > Are you able to try a slightly more experimental kernel?
> >
> > -chris
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-03-22  6:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21  8:03 No space left on device (28) Stefan Priebe - Profihost AG
2013-03-21 18:00 ` Chris Mason
2013-03-21 18:35   ` Stefan Priebe - Profihost AG
2013-03-21 19:02     ` Chris Mason
2013-03-21 19:42       ` Stefan Priebe
2013-03-22  6:08         ` Stefan Priebe - Profihost AG
2013-03-22 12:11           ` Stefan Priebe - Profihost AG
2013-03-22 13:53             ` Josef Bacik
2013-03-22 13:56               ` Stefan Priebe - Profihost AG
2013-03-22 15:54                 ` Josef Bacik
2013-03-22 19:10                   ` Stefan Priebe
2013-03-22 20:49                     ` Josef Bacik
2013-03-22 20:55                       ` Stefan Priebe
2013-03-25 20:14                         ` Josef Bacik
2013-03-26  7:45                           ` Stefan Priebe
2013-03-26 12:53                             ` Josef Bacik
2013-03-26 12:55                               ` Stefan Priebe - Profihost AG
2013-03-26 13:30                                 ` Josef Bacik
2013-03-26 13:49                                   ` Stefan Priebe - Profihost AG
2013-03-26 14:44                                     ` Josef Bacik
2013-03-26 15:03                                       ` Stefan Priebe - Profihost AG
2013-03-26 15:25                                         ` Josef Bacik
2013-03-26 16:19                                           ` Stefan Priebe
2013-03-26 17:45                                             ` Josef Bacik
2013-03-26 19:05                                               ` Stefan Priebe
2013-03-26 19:16                                                 ` Josef Bacik
2013-03-26 19:22                                                   ` Stefan Priebe
2013-03-26 19:38                                                     ` Josef Bacik
2013-03-26 19:47                                                       ` Stefan Priebe
2013-03-22  6:13         ` Roman Mamedov [this message]
2013-03-22  6:24           ` cwillu
2013-03-22  6:39             ` Stefan Priebe - Profihost AG
2013-03-22  6:41               ` cwillu
2013-03-22  7:06                 ` Stefan Priebe - Profihost AG
2013-03-22  6:38           ` Stefan Priebe - Profihost AG

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=20130322121356.237e57e8@natsu \
    --to=rm@romanrm.ru \
    --cc=clmason@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=s.priebe@profihost.ag \
    /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