* Re: no space left on device
[not found] <AANLkTinH225vC8fRbA7zk_iOEmyADFZMBS6b7gx1tOxm@mail.gmail.com>
@ 2011-02-08 9:00 ` Leonidas Spyropoulos
2011-02-08 9:31 ` cwillu
0 siblings, 1 reply; 33+ messages in thread
From: Leonidas Spyropoulos @ 2011-02-08 9:00 UTC (permalink / raw)
To: C Anthony Risinger; +Cc: linux-btrfs
On Feb 8, 2011 12:09 AM, "C Anthony Risinger" <anthony@extof.me> wrote:
>
> On Mon, Feb 7, 2011 at 3:21 PM, Leonidas Spyropoulos
> <artafinde@gmail.com> wrote:
> > Hey all,
> >
> > I run into no space left on device on a virtualbox
> >
> > After installing Debian 6 on a virtual machine
> > I tried installing the KDE desktop
> >
> > The system HDD is 8Gb
> > Both root (/) and /home are btrfs
> > over LVM.
> >
> > While installing the packages I run into:
> >
> > no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_used, 0
> > bytes_reserved,
> > 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total
> >
> > df shows only 74% used space on /
> >
> > kernel used: stock debian 6 2.6.32-5-686
> >
> > At the moment I cannot access it with normal boot, only recovery mode.
> >
> > I can provide whatever info you would like as long as you think of a
> > way to load the normal system and not the recovery mode.
>
> IIRC .32 has all sorts of ENOSPC problems; I think this was seriously
> tackled in kernels > .32... this kernel was only declared ready for
> "early adopters", with an "expect issues" disclaimer.
>
> The btrfs-tools in squeeze is probably so old you may not even have
> the `btrfs` binary, but I don't run debian so I'm not sure there...
> not really a solution probably for you, but I wouldn't run that kernel
> if using btrfs.
>
> C Anthony
Hey all,
Thanks for all the answers.
The problem is that I cannot login to the system.only recovery mode works,
and there btrfs command is not there as you imagined.
I will try though ssh but I don't think it's installed by default and I
cannot install it.
So the next step is try from recovery console of debian live cd, which still
has the really old tools...
I think this is quite some serious issue but generally all debian's fault
adopting a btrfs file system support on a 2.6.32 kernel and without
btrfs-progs on some decent version.
I'll update when possible.
Please throw any other alternatives my way anyone.
Thanks,
Leonidas
--
Caution: breathing may be hazardous to your health.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2011-02-08 9:00 ` no space left on device Leonidas Spyropoulos
@ 2011-02-08 9:31 ` cwillu
2011-02-08 10:08 ` Leonidas Spyropoulos
0 siblings, 1 reply; 33+ messages in thread
From: cwillu @ 2011-02-08 9:31 UTC (permalink / raw)
To: Leonidas Spyropoulos; +Cc: C Anthony Risinger, linux-btrfs
On Tue, Feb 8, 2011 at 3:00 AM, Leonidas Spyropoulos
<artafinde@gmail.com> wrote:
> On Feb 8, 2011 12:09 AM, "C Anthony Risinger" <anthony@extof.me> wrote:
>>
>> On Mon, Feb 7, 2011 at 3:21 PM, Leonidas Spyropoulos
>> <artafinde@gmail.com> wrote:
>> > Hey all,
>> >
>> > I run into no space left on device on a virtualbox
>> >
>> > After installing Debian 6 on a virtual machine
>> > I tried installing the KDE desktop
>> >
>> > The system HDD is 8Gb
>> > Both root (/) and /home are btrfs
>> > over LVM.
>> >
>> > While installing the packages I run into:
>> >
>> > no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_used, 0
>> > bytes_reserved,
>> > 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total
>> >
>> > df shows only 74% used space on /
>> >
>> > kernel used: stock debian 6 2.6.32-5-686
>> >
>> > At the moment I cannot access it with normal boot, only recovery mode.
>> >
>> > I can provide whatever info you would like as long as you think of a
>> > way to load the normal system and not the recovery mode.
>>
>> IIRC .32 has all sorts of ENOSPC problems; I think this was seriously
>> tackled in kernels > .32... this kernel was only declared ready for
>> "early adopters", with an "expect issues" disclaimer.
>>
>> The btrfs-tools in squeeze is probably so old you may not even have
>> the `btrfs` binary, but I don't run debian so I'm not sure there...
>> not really a solution probably for you, but I wouldn't run that kernel
>> if using btrfs.
>>
>> C Anthony
>
> Hey all,
>
> Thanks for all the answers.
>
> The problem is that I cannot login to the system.only recovery mode works,
> and there btrfs command is not there as you imagined.
>
> I will try though ssh but I don't think it's installed by default and I
> cannot install it.
>
> So the next step is try from recovery console of debian live cd, which still
> has the really old tools...
>
> I think this is quite some serious issue but generally all debian's fault
> adopting a btrfs file system support on a 2.6.32 kernel and without
> btrfs-progs on some decent version.
>
> I'll update when possible.
> Please throw any other alternatives my way anyone.
I have to be blunt, blaming your problems on debian isn't terribly
classy. The "oooo, shiny!" reflex is your fault, not debian's.
Download and install a prebuilt 2.6.35 or later kernel into your /boot
via a livecd or whatever, unpack and add the btrfs command to the
initramfs for that kernel, boot up into that initramfs with the kernel
option "break=premount", and fix the rootfs from the busybox prompt.
Alternatively, an ubuntu natty alpha livecd has a 2.6.38 kernel, and
you can install mostly up-to-date btrfs tools into that environment.
I'm sure debian has something similar available.
--Carey Underwood
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2011-02-08 9:31 ` cwillu
@ 2011-02-08 10:08 ` Leonidas Spyropoulos
2011-02-08 13:19 ` Helmut Hullen
0 siblings, 1 reply; 33+ messages in thread
From: Leonidas Spyropoulos @ 2011-02-08 10:08 UTC (permalink / raw)
To: cwillu; +Cc: C Anthony Risinger, linux-btrfs
On 8 February 2011 09:31, cwillu <cwillu@cwillu.com> wrote:
> On Tue, Feb 8, 2011 at 3:00 AM, Leonidas Spyropoulos
> <artafinde@gmail.com> wrote:
>> On Feb 8, 2011 12:09 AM, "C Anthony Risinger" <anthony@extof.me> wro=
te:
>>>
>>> On Mon, Feb 7, 2011 at 3:21 PM, Leonidas Spyropoulos
>>> <artafinde@gmail.com> wrote:
>>> > Hey all,
>>> >
>>> > I run into no space left on device on a virtualbox
>>> >
>>> > After installing Debian 6 on a virtual machine
>>> > I tried installing the KDE desktop
>>> >
>>> > The system HDD is 8Gb
>>> > Both root (/) and /home are btrfs
>>> > over LVM.
>>> >
>>> > While installing the packages I run into:
>>> >
>>> > no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_us=
ed, 0
>>> > bytes_reserved,
>>> > 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total
>>> >
>>> > df shows only 74% used space on /
>>> >
>>> > kernel used: stock debian 6 2.6.32-5-686
>>> >
>>> > At the moment I cannot access it with normal boot, only recovery =
mode.
>>> >
>>> > I can provide whatever info you would like as long as you think o=
f a
>>> > way to load the normal system and not the recovery mode.
>>>
>>> IIRC .32 has all sorts of ENOSPC problems; I think this was serious=
ly
>>> tackled in kernels > .32... this kernel was only declared ready for
>>> "early adopters", with an "expect issues" disclaimer.
>>>
>>> The btrfs-tools in squeeze is probably so old you may not even have
>>> the `btrfs` binary, but I don't run debian so I'm not sure there...
>>> not really a solution probably for you, but I wouldn't run that ker=
nel
>>> if using btrfs.
>>>
>>> C Anthony
>>
>> Hey all,
>>
>> Thanks for all the answers.
>>
>> The problem is that I cannot login to the system.only recovery mode =
works,
>> and there btrfs command is not there as you imagined.
>>
>> I will try though ssh but I don't think it's installed by default an=
d I
>> cannot install it.
>>
>> So the next step is try from recovery console of debian live cd, whi=
ch still
>> has the really old tools...
>>
>> I think this is quite some serious issue but generally all debian's =
fault
>> adopting a btrfs file system support on a 2.6.32 kernel and without
>> btrfs-progs on some decent version.
>>
>> I'll update when possible.
>> Please throw any other alternatives my way anyone.
>
> I have to be blunt, blaming your problems on debian isn't terribly
> classy. =A0The "oooo, shiny!" reflex is your fault, not debian's.
Well you are right it is my problem and yeah I wanted to test the "new
shiny" Debian 6 with
officially btrfs supported.
=46or the moment I apt-get clean to get some space since my / was
updating the KDE (so it had a lot of cache files there)
Reserved something like 300Mb and then vlextend the /
But the next step is to update kernel and btrfs-progs from git.
Thanks for answers
>
> Download and install a prebuilt 2.6.35 or later kernel into your /boo=
t
> via a livecd or whatever, unpack and add the btrfs command to the
> initramfs for that kernel, boot up into that initramfs with the kerne=
l
> option "break=3Dpremount", and fix the rootfs from the busybox prompt=
=2E
The above seems unknown to me. Could you elaborate a bit please?
>
> Alternatively, an ubuntu natty alpha livecd has a 2.6.38 kernel, and
> you can install mostly up-to-date btrfs tools into that environment.
> I'm sure debian has something similar available.
I was wondering how to fix this without liveCD.
>
> --Carey Underwood
>
--=20
Caution: breathing may be hazardous to your health.
--
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
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2011-02-08 10:08 ` Leonidas Spyropoulos
@ 2011-02-08 13:19 ` Helmut Hullen
2011-02-08 18:56 ` Erik Logtenberg
0 siblings, 1 reply; 33+ messages in thread
From: Helmut Hullen @ 2011-02-08 13:19 UTC (permalink / raw)
To: linux-btrfs
Hallo, Leonidas,
Du meintest am 08.02.11:
[...]
>> I have to be blunt, blaming your problems on debian isn't terribly
>> classy. =A0The "oooo, shiny!" reflex is your fault, not debian's.
> Well you are right it is my problem and yeah I wanted to test the
> "new shiny" Debian 6 with officially btrfs supported.
It's my problem too - I have to restore about 1.5 TByte somehow ...
> For the moment I apt-get clean to get some space since my / was
> updating the KDE (so it had a lot of cache files there)
> Reserved something like 300Mb and then vlextend the /
> But the next step is to update kernel and btrfs-progs from git.
Maybe that doesn't help now. I'm working with kernel 2.6.37 and kernel =
=20
2.6.38-rc2, and I've got big problems.
Viele Gruesse!
Helmut
--
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
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2011-02-08 13:19 ` Helmut Hullen
@ 2011-02-08 18:56 ` Erik Logtenberg
2011-02-08 19:43 ` Helmut Hullen
` (2 more replies)
0 siblings, 3 replies; 33+ messages in thread
From: Erik Logtenberg @ 2011-02-08 18:56 UTC (permalink / raw)
To: linux-btrfs
>> But the next step is to update kernel and btrfs-progs from git.
>
> Maybe that doesn't help now. I'm working with kernel 2.6.37 and kernel
> 2.6.38-rc2, and I've got big problems.
I had to install at least 2.6.37 to have a kernel with an advanced
enough balance feature to actually reclaim the free space and report it
correctly too.
Still, I had so much kernel crashes during this balance operation that
even after numerous retries I still hadn't once completed it (on a FS of
merely 300GB). Fortunately Zheng Yan coded a patch, which I applied to
2.6.38-rc2, so that I could finally run - and finish - the balance
operation.
Additionally this version of btrfs is more clever in not wasting the
free space to begin with, hence making future rebalances for reclaiming
free space no longer necessary.
That patch is released on this list on january 26th, called "Fix balance
panic". If you experience the same, you could try applying this patch
too. There is no (pre-built) kernel yet with this patch already applied.
- Erik.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2011-02-08 18:56 ` Erik Logtenberg
@ 2011-02-08 19:43 ` Helmut Hullen
2011-02-12 14:11 ` Erik Logtenberg
2011-02-08 20:36 ` Helmut Hullen
2011-02-09 12:41 ` kernel panic (was: no space left on device) Helmut Hullen
2 siblings, 1 reply; 33+ messages in thread
From: Helmut Hullen @ 2011-02-08 19:43 UTC (permalink / raw)
To: linux-btrfs
Hallo, Erik,
Du meintest am 08.02.11:
>>> But the next step is to update kernel and btrfs-progs from git.
>> Maybe that doesn't help now. I'm working with kernel 2.6.37 and
>> kernel 2.6.38-rc2, and I've got big problems.
[...]
> Fortunately Zheng Yan coded a patch, which I
> applied to 2.6.38-rc2, so that I could finally run - and finish - the
> balance operation.
[...]
> That patch is released on this list on january 26th, called "Fix
> balance panic". If you experience the same, you could try applying
> this patch too. There is no (pre-built) kernel yet with this patch
> already applied.
Maybe it will help. But my actual problem is: I cannot mount the btrfs
system (it leads to "kernel panic"). And starting "btrfs filesystem
balance ..." requires a mounted btrfs system.
I'll see ...
Viele Gruesse!
Helmut
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2011-02-08 19:43 ` Helmut Hullen
@ 2011-02-12 14:11 ` Erik Logtenberg
0 siblings, 0 replies; 33+ messages in thread
From: Erik Logtenberg @ 2011-02-12 14:11 UTC (permalink / raw)
To: helmut; +Cc: linux-btrfs
>> That patch is released on this list on january 26th, called "Fix
>> balance panic". If you experience the same, you could try applying
>> this patch too. There is no (pre-built) kernel yet with this patch
>> already applied.
>
> Maybe it will help. But my actual problem is: I cannot mount the btrfs
> system (it leads to "kernel panic"). And starting "btrfs filesystem
> balance ..." requires a mounted btrfs system.
Yeah sorry, I hadn't noticed that. No, that patch will certainly not fix
a filesystem you can't mount to begin with. Can't help you out.
- Erik
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2011-02-08 18:56 ` Erik Logtenberg
2011-02-08 19:43 ` Helmut Hullen
@ 2011-02-08 20:36 ` Helmut Hullen
2011-02-09 12:41 ` kernel panic (was: no space left on device) Helmut Hullen
2 siblings, 0 replies; 33+ messages in thread
From: Helmut Hullen @ 2011-02-08 20:36 UTC (permalink / raw)
To: linux-btrfs
Hallo, Erik,
Du meintest am 08.02.11:
[...]
> Fortunately Zheng Yan coded a patch, which I
> applied to 2.6.38-rc2, so that I could finally run - and finish - the
> balance operation.
> Additionally this version of btrfs is more clever in not wasting the
> free space to begin with, hence making future rebalances for
> reclaiming free space no longer necessary.
That patch isn't yet included in 2.6.38-rc4.
Viele Gruesse!
Helmut
^ permalink raw reply [flat|nested] 33+ messages in thread
* kernel panic (was: no space left on device)
2011-02-08 18:56 ` Erik Logtenberg
2011-02-08 19:43 ` Helmut Hullen
2011-02-08 20:36 ` Helmut Hullen
@ 2011-02-09 12:41 ` Helmut Hullen
2 siblings, 0 replies; 33+ messages in thread
From: Helmut Hullen @ 2011-02-09 12:41 UTC (permalink / raw)
To: linux-btrfs
Hallo, Erik,
Du meintest am 08.02.11:
>> Maybe that doesn't help now. I'm working with kernel 2.6.37 and
>> kernel 2.6.38-rc2, and I've got big problems.
> I had to install at least 2.6.37 to have a kernel with an advanced
> enough balance feature to actually reclaim the free space and report
> it correctly too.
> Still, I had so much kernel crashes during this balance operation
> that even after numerous retries I still hadn't once completed it (on
> a FS of merely 300GB). Fortunately Zheng Yan coded a patch, which I
> applied to 2.6.38-rc2, so that I could finally run - and finish - the
> balance operation.
Didn't help - sorry.
You can take a look to the last lines of my system after crashing into
"kernel panic" with blinkenlights:
http://helmut.hullen.de/btrfs/
The screenshots are hard to read - sorry.
Viele Gruesse!
Helmut
^ permalink raw reply [flat|nested] 33+ messages in thread
* No space left on device
@ 2014-02-12 9:51 Jakob Truelsen
2014-02-12 10:26 ` Hugo Mills
2014-02-12 10:34 ` Leonidas Spyropoulos
0 siblings, 2 replies; 33+ messages in thread
From: Jakob Truelsen @ 2014-02-12 9:51 UTC (permalink / raw)
To: linux-btrfs
Hello. I am experiencing "No space left on device" with a btrfs file
system, yet I cannot seem to find any exhausted resource. Could some
resource I do not know about be exhausted, or is this caused by
something else. Below is a trace of information that might be usefull,
please let me know if there is anything I can do to resolve the issue.
/Jakob
[jakobt@soda ~]$ uname -a
Linux soda 3.12.8-1-ARCH #1 SMP PREEMPT Thu Jan 16 09:16:34 CET 2014
x86_64 GNU/Linux
[jakobt@soda ~]$ btrfs --version
Btrfs v3.12
[jakobt@soda ~]$ mount
...
/dev/sda on /data type btrfs (rw,relatime,nospace_cache)
[jakobt@soda ~]$ df /data
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb2 76594224 49247368 23433028 68% /
[jakobt@soda ~]$ btrfs filesystem df /data
Data, single: total=1.82TiB, used=518.04GiB
System, DUP: total=8.00MiB, used=204.00KiB
System, single: total=4.00MiB, used=0.00
Metadata, DUP: total=1.00GiB, used=767.70MiB
Metadata, single: total=8.00MiB, used=0.00
[jakobt@soda ~]$ touch /data/jakobt/hat
touch: cannot touch ‘/data/jakobt/hat’: No space left on device
[jakobt@soda ~]$ sudo btrfs fi balance start /data
ERROR: error during balancing '/data' - No space left on device
There may be more info in syslog - try dmesg | tail
[jakobt@soda ~]$ dmesg | grep tail -n 2
[1113177.878157] btrfs: device label Data devid 1 transid 44784 /dev/sda
[1113507.641752] btrfs: 1866 enospc errors during balance
[jakobt@soda ~]$ sudo umount /data
[jakobt@soda ~]$ sudo btrfsck /dev/sda
...
cache and super generation don't match, space cache will be invalidated
..
found 172181366447 bytes used err is 0
total csum bytes: 418841160
total tree bytes: 805187584
total fs tree bytes: 247164928
total extent tree bytes: 26329088
btree space waste bytes: 164771401
file data blocks allocated: 561564688384
referenced 511759908864
Btrfs v3.12
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: No space left on device
2014-02-12 9:51 No space left on device Jakob Truelsen
@ 2014-02-12 10:26 ` Hugo Mills
2014-02-12 10:45 ` Jakob Truelsen
2014-02-12 10:34 ` Leonidas Spyropoulos
1 sibling, 1 reply; 33+ messages in thread
From: Hugo Mills @ 2014-02-12 10:26 UTC (permalink / raw)
To: Jakob Truelsen; +Cc: linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 3295 bytes --]
On Wed, Feb 12, 2014 at 10:51:12AM +0100, Jakob Truelsen wrote:
> Hello. I am experiencing "No space left on device" with a btrfs file
> system, yet I cannot seem to find any exhausted resource. Could some
> resource I do not know about be exhausted, or is this caused by
> something else. Below is a trace of information that might be usefull,
> please let me know if there is anything I can do to resolve the issue.
>
> /Jakob
>
> [jakobt@soda ~]$ uname -a
> Linux soda 3.12.8-1-ARCH #1 SMP PREEMPT Thu Jan 16 09:16:34 CET 2014
> x86_64 GNU/Linux
Were you using this kernel when the problem happened?
> [jakobt@soda ~]$ btrfs --version
> Btrfs v3.12
>
> [jakobt@soda ~]$ mount
> ...
> /dev/sda on /data type btrfs (rw,relatime,nospace_cache)
>
> [jakobt@soda ~]$ df /data
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sdb2 76594224 49247368 23433028 68% /
>
> [jakobt@soda ~]$ btrfs filesystem df /data
> Data, single: total=1.82TiB, used=518.04GiB
> System, DUP: total=8.00MiB, used=204.00KiB
> System, single: total=4.00MiB, used=0.00
> Metadata, DUP: total=1.00GiB, used=767.70MiB
^^^ This is your problem, most likely in conjunction with all the
space on the device being allocated. Being a copy-on-write filesystem,
btrfs needs free space to make any update. If it doesn't have that
free space, you get "No space left on device". You typically need
somewhere around 0.5-1 GiB of headroom in metadata for normal
operation, so I'm surprised you got this far. :)
The FS should normally allocate more metadata space as it needs it,
but because (I think) your data allocation has taken up all the
available space on the device, there's no way for it to add more.
> Metadata, single: total=8.00MiB, used=0.00
> [jakobt@soda ~]$ touch /data/jakobt/hat
> touch: cannot touch ‘/data/jakobt/hat’: No space left on device
>
> [jakobt@soda ~]$ sudo btrfs fi balance start /data
> ERROR: error during balancing '/data' - No space left on device
> There may be more info in syslog - try dmesg | tail
Try:
btrfs balance start -dusage=0 /data
which should go looking for entirely unused block groups and reclaim
those. (If you don't use the -dusage= parameter, it will try to
balance everything, which takes a long time).
> [jakobt@soda ~]$ dmesg | grep tail -n 2
> [1113177.878157] btrfs: device label Data devid 1 transid 44784 /dev/sda
> [1113507.641752] btrfs: 1866 enospc errors during balance
Although, that said... it looks like it's tried every block group
and failed with each one, so my suggestion above may not work in this
instance.
Let us know what happens with the balance command above anyway
(dmesg output is useful information at this point). If that doesn't
help, then we'll probably need to take a metadata image and throw it
in josef's direction, where he will start crying at having to deal
with enospc problems again. :)
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- If you're not part of the solution, you're part ---
of the precipiate.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: No space left on device
2014-02-12 10:26 ` Hugo Mills
@ 2014-02-12 10:45 ` Jakob Truelsen
2014-02-12 11:07 ` Hugo Mills
0 siblings, 1 reply; 33+ messages in thread
From: Jakob Truelsen @ 2014-02-12 10:45 UTC (permalink / raw)
To: Hugo Mills, Jakob Truelsen, linux-btrfs
Hi and thanks for the quick reply. Have remounted the filesystem with
enospc_debug, and run the rebalance you suggested, with the trance
below. So perhaps the next step is for me to figure out how to take a
metadata image and send it to josef (perhaps with a box of tissues)
/Jakob
[jakobt@soda ~]$ mount
...
/dev/sda on /data type btrfs (rw,relatime,nospace_cache,enospc_debug)
[jakobt@soda ~]$ sudo btrfs balance start -dusage=0 /data
ERROR: error during balancing '/data' - No space left on device
There may be more info in syslog - try dmesg | tail
[jakobt@soda ~]$ touch /data/jakobt/monkey
touch: cannot touch ‘/data/jakobt/monkey’: No space left on device
[jakobt@soda ~]$ dmesg | tail -n3
[1117530.870965] btrfs: device label Data devid 1 transid 47091 /dev/sda
[1117573.087580] btrfs: 426 enospc errors during balance
[1117642.002437] btrfs: 426 enospc errors during balance
On Wed, Feb 12, 2014 at 11:26 AM, Hugo Mills <hugo@carfax.org.uk> wrote:
> On Wed, Feb 12, 2014 at 10:51:12AM +0100, Jakob Truelsen wrote:
>> Hello. I am experiencing "No space left on device" with a btrfs file
>> system, yet I cannot seem to find any exhausted resource. Could some
>> resource I do not know about be exhausted, or is this caused by
>> something else. Below is a trace of information that might be usefull,
>> please let me know if there is anything I can do to resolve the issue.
>>
>> /Jakob
>>
>> [jakobt@soda ~]$ uname -a
>> Linux soda 3.12.8-1-ARCH #1 SMP PREEMPT Thu Jan 16 09:16:34 CET 2014
>> x86_64 GNU/Linux
>
> Were you using this kernel when the problem happened?
>
>> [jakobt@soda ~]$ btrfs --version
>> Btrfs v3.12
>>
>> [jakobt@soda ~]$ mount
>> ...
>> /dev/sda on /data type btrfs (rw,relatime,nospace_cache)
>>
>> [jakobt@soda ~]$ df /data
>> Filesystem 1K-blocks Used Available Use% Mounted on
>> /dev/sdb2 76594224 49247368 23433028 68% /
>>
>> [jakobt@soda ~]$ btrfs filesystem df /data
>> Data, single: total=1.82TiB, used=518.04GiB
>> System, DUP: total=8.00MiB, used=204.00KiB
>> System, single: total=4.00MiB, used=0.00
>> Metadata, DUP: total=1.00GiB, used=767.70MiB
>
> ^^^ This is your problem, most likely in conjunction with all the
> space on the device being allocated. Being a copy-on-write filesystem,
> btrfs needs free space to make any update. If it doesn't have that
> free space, you get "No space left on device". You typically need
> somewhere around 0.5-1 GiB of headroom in metadata for normal
> operation, so I'm surprised you got this far. :)
>
> The FS should normally allocate more metadata space as it needs it,
> but because (I think) your data allocation has taken up all the
> available space on the device, there's no way for it to add more.
>
>> Metadata, single: total=8.00MiB, used=0.00
>
>> [jakobt@soda ~]$ touch /data/jakobt/hat
>> touch: cannot touch ‘/data/jakobt/hat’: No space left on device
>>
>> [jakobt@soda ~]$ sudo btrfs fi balance start /data
>> ERROR: error during balancing '/data' - No space left on device
>> There may be more info in syslog - try dmesg | tail
>
> Try:
>
> btrfs balance start -dusage=0 /data
>
> which should go looking for entirely unused block groups and reclaim
> those. (If you don't use the -dusage= parameter, it will try to
> balance everything, which takes a long time).
>
>> [jakobt@soda ~]$ dmesg | grep tail -n 2
>> [1113177.878157] btrfs: device label Data devid 1 transid 44784 /dev/sda
>> [1113507.641752] btrfs: 1866 enospc errors during balance
>
> Although, that said... it looks like it's tried every block group
> and failed with each one, so my suggestion above may not work in this
> instance.
>
> Let us know what happens with the balance command above anyway
> (dmesg output is useful information at this point). If that doesn't
> help, then we'll probably need to take a metadata image and throw it
> in josef's direction, where he will start crying at having to deal
> with enospc problems again. :)
>
> Hugo.
>
> --
> === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
> PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
> --- If you're not part of the solution, you're part ---
> of the precipiate.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: No space left on device
2014-02-12 10:45 ` Jakob Truelsen
@ 2014-02-12 11:07 ` Hugo Mills
0 siblings, 0 replies; 33+ messages in thread
From: Hugo Mills @ 2014-02-12 11:07 UTC (permalink / raw)
To: Jakob Truelsen; +Cc: linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 5136 bytes --]
On Wed, Feb 12, 2014 at 11:45:34AM +0100, Jakob Truelsen wrote:
> Hi and thanks for the quick reply. Have remounted the filesystem with
> enospc_debug, and run the rebalance you suggested, with the trance
> below. So perhaps the next step is for me to figure out how to take a
> metadata image and send it to josef (perhaps with a box of tissues)
You can get the metadata image with:
btrfs-image -c9 -t4 /dev/sda image-file-to-create
It will probably be a couple of hundred megabytes in size (your
metadata size, compressed). It will contain filenames and xattrs, so
if those are sensitive, you may want to use -s to hide that
information.
After that, probably the best place to make sure it's not lost is
to open an issue on bugzilla.kernel.org, making sure that you set the
Component to btrfs.
Hugo.
> /Jakob
>
>
> [jakobt@soda ~]$ mount
> ...
> /dev/sda on /data type btrfs (rw,relatime,nospace_cache,enospc_debug)
>
> [jakobt@soda ~]$ sudo btrfs balance start -dusage=0 /data
> ERROR: error during balancing '/data' - No space left on device
> There may be more info in syslog - try dmesg | tail
>
> [jakobt@soda ~]$ touch /data/jakobt/monkey
> touch: cannot touch ‘/data/jakobt/monkey’: No space left on device
>
> [jakobt@soda ~]$ dmesg | tail -n3
> [1117530.870965] btrfs: device label Data devid 1 transid 47091 /dev/sda
> [1117573.087580] btrfs: 426 enospc errors during balance
> [1117642.002437] btrfs: 426 enospc errors during balance
> On Wed, Feb 12, 2014 at 11:26 AM, Hugo Mills <hugo@carfax.org.uk> wrote:
> > On Wed, Feb 12, 2014 at 10:51:12AM +0100, Jakob Truelsen wrote:
> >> Hello. I am experiencing "No space left on device" with a btrfs file
> >> system, yet I cannot seem to find any exhausted resource. Could some
> >> resource I do not know about be exhausted, or is this caused by
> >> something else. Below is a trace of information that might be usefull,
> >> please let me know if there is anything I can do to resolve the issue.
> >>
> >> /Jakob
> >>
> >> [jakobt@soda ~]$ uname -a
> >> Linux soda 3.12.8-1-ARCH #1 SMP PREEMPT Thu Jan 16 09:16:34 CET 2014
> >> x86_64 GNU/Linux
> >
> > Were you using this kernel when the problem happened?
> >
> >> [jakobt@soda ~]$ btrfs --version
> >> Btrfs v3.12
> >>
> >> [jakobt@soda ~]$ mount
> >> ...
> >> /dev/sda on /data type btrfs (rw,relatime,nospace_cache)
> >>
> >> [jakobt@soda ~]$ df /data
> >> Filesystem 1K-blocks Used Available Use% Mounted on
> >> /dev/sdb2 76594224 49247368 23433028 68% /
> >>
> >> [jakobt@soda ~]$ btrfs filesystem df /data
> >> Data, single: total=1.82TiB, used=518.04GiB
> >> System, DUP: total=8.00MiB, used=204.00KiB
> >> System, single: total=4.00MiB, used=0.00
> >> Metadata, DUP: total=1.00GiB, used=767.70MiB
> >
> > ^^^ This is your problem, most likely in conjunction with all the
> > space on the device being allocated. Being a copy-on-write filesystem,
> > btrfs needs free space to make any update. If it doesn't have that
> > free space, you get "No space left on device". You typically need
> > somewhere around 0.5-1 GiB of headroom in metadata for normal
> > operation, so I'm surprised you got this far. :)
> >
> > The FS should normally allocate more metadata space as it needs it,
> > but because (I think) your data allocation has taken up all the
> > available space on the device, there's no way for it to add more.
> >
> >> Metadata, single: total=8.00MiB, used=0.00
> >
> >> [jakobt@soda ~]$ touch /data/jakobt/hat
> >> touch: cannot touch ‘/data/jakobt/hat’: No space left on device
> >>
> >> [jakobt@soda ~]$ sudo btrfs fi balance start /data
> >> ERROR: error during balancing '/data' - No space left on device
> >> There may be more info in syslog - try dmesg | tail
> >
> > Try:
> >
> > btrfs balance start -dusage=0 /data
> >
> > which should go looking for entirely unused block groups and reclaim
> > those. (If you don't use the -dusage= parameter, it will try to
> > balance everything, which takes a long time).
> >
> >> [jakobt@soda ~]$ dmesg | grep tail -n 2
> >> [1113177.878157] btrfs: device label Data devid 1 transid 44784 /dev/sda
> >> [1113507.641752] btrfs: 1866 enospc errors during balance
> >
> > Although, that said... it looks like it's tried every block group
> > and failed with each one, so my suggestion above may not work in this
> > instance.
> >
> > Let us know what happens with the balance command above anyway
> > (dmesg output is useful information at this point). If that doesn't
> > help, then we'll probably need to take a metadata image and throw it
> > in josef's direction, where he will start crying at having to deal
> > with enospc problems again. :)
> >
> > Hugo.
> >
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- If you're not part of the solution, you're part ---
of the precipiate.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: No space left on device
2014-02-12 9:51 No space left on device Jakob Truelsen
2014-02-12 10:26 ` Hugo Mills
@ 2014-02-12 10:34 ` Leonidas Spyropoulos
1 sibling, 0 replies; 33+ messages in thread
From: Leonidas Spyropoulos @ 2014-02-12 10:34 UTC (permalink / raw)
To: Jakob Truelsen, linux-btrfs
On 12/02/2014 09:51, Jakob Truelsen wrote:
> Hello. I am experiencing "No space left on device" with a btrfs file
> system, yet I cannot seem to find any exhausted resource. Could some
> resource I do not know about be exhausted, or is this caused by
> something else. Below is a trace of information that might be usefull,
> please let me know if there is anything I can do to resolve the issue.
>
> /Jakob
>
> [jakobt@soda ~]$ uname -a
> Linux soda 3.12.8-1-ARCH #1 SMP PREEMPT Thu Jan 16 09:16:34 CET 2014
> x86_64 GNU/Linux
>
> [jakobt@soda ~]$ btrfs --version
> Btrfs v3.12
>
> [jakobt@soda ~]$ mount
> ...
> /dev/sda on /data type btrfs (rw,relatime,nospace_cache)
>
> [jakobt@soda ~]$ df /data
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sdb2 76594224 49247368 23433028 68% /
>
> [jakobt@soda ~]$ btrfs filesystem df /data
> Data, single: total=1.82TiB, used=518.04GiB
> System, DUP: total=8.00MiB, used=204.00KiB
> System, single: total=4.00MiB, used=0.00
> Metadata, DUP: total=1.00GiB, used=767.70MiB
> Metadata, single: total=8.00MiB, used=0.00
>
> [jakobt@soda ~]$ touch /data/jakobt/hat
> touch: cannot touch ‘/data/jakobt/hat’: No space left on device
>
> [jakobt@soda ~]$ sudo btrfs fi balance start /data
> ERROR: error during balancing '/data' - No space left on device
> There may be more info in syslog - try dmesg | tail
>
> [jakobt@soda ~]$ dmesg | grep tail -n 2
> [1113177.878157] btrfs: device label Data devid 1 transid 44784 /dev/sda
> [1113507.641752] btrfs: 1866 enospc errors during balance
>
> [jakobt@soda ~]$ sudo umount /data
>
> [jakobt@soda ~]$ sudo btrfsck /dev/sda
> ...
> cache and super generation don't match, space cache will be invalidated
> ..
> found 172181366447 bytes used err is 0
> total csum bytes: 418841160
> total tree bytes: 805187584
> total fs tree bytes: 247164928
> total extent tree bytes: 26329088
> btree space waste bytes: 164771401
> file data blocks allocated: 561564688384
> referenced 511759908864
> Btrfs v3.12
> --
> 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
>
Hello Jacob,
Have you tried balancing just the data/metadata chunks only?
Regards,
Leonidas
^ permalink raw reply [flat|nested] 33+ messages in thread
* no space left on device.
@ 2012-11-01 13:35 Kenneth Johansson
2012-11-02 15:54 ` Kyle Gates
0 siblings, 1 reply; 33+ messages in thread
From: Kenneth Johansson @ 2012-11-01 13:35 UTC (permalink / raw)
To: linux-btrfs
So I have ended up in a state where I can't delete files with rm.
the error I get is no space on device. however I'm not even close to empty.
/dev/sdb1 38G 27G 9.5G 75%
there is about 800k files/dirs in this filesystem
extra strange is that I can in another directory create and delete files.
So I tried pretty much all I could google my way to but problem
persisted. So I decided to do a backup and a format. But when the backup
was done I tried one more time and now it was possible to delete the
directory and all content?
using the 3.5 kernel in ubuntu 12.10. Is this a known issue ? is it
fixed in later kernels?
fsck /btrfs scrub and kernel log. nothing indicate any problem of any kind.
^ permalink raw reply [flat|nested] 33+ messages in thread
* RE: no space left on device.
2012-11-01 13:35 no " Kenneth Johansson
@ 2012-11-02 15:54 ` Kyle Gates
2012-11-02 15:59 ` Hugo Mills
2012-11-06 13:23 ` Kenneth Johansson
0 siblings, 2 replies; 33+ messages in thread
From: Kyle Gates @ 2012-11-02 15:54 UTC (permalink / raw)
To: Kenneth Johansson, linux-btrfs@vger.kernel.org
> So I have ended up in a state where I can't delete files with rm.
>
> the error I get is no space on device. however I'm not even close to empty.
> /dev/sdb1 38G 27G 9.5G 75%
> there is about 800k files/dirs in this filesystem
>
> extra strange is that I can in another directory create and delete files.
>
> So I tried pretty much all I could google my way to but problem
> persisted. So I decided to do a backup and a format. But when the backup
> was done I tried one more time and now it was possible to delete the
> directory and all content?
>
> using the 3.5 kernel in ubuntu 12.10. Is this a known issue ? is it
> fixed in later kernels?
>
> fsck /btrfs scrub and kernel log. nothing indicate any problem of any kind.
>
First let's see the output of:
btrfs fi df /mountpoint
You're probably way over allocated in metadata so a balance should help:
btrfs bal start -m /mountpoint
or omit the -m option to run a full balance.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device.
2012-11-02 15:54 ` Kyle Gates
@ 2012-11-02 15:59 ` Hugo Mills
2012-11-06 13:23 ` Kenneth Johansson
1 sibling, 0 replies; 33+ messages in thread
From: Hugo Mills @ 2012-11-02 15:59 UTC (permalink / raw)
To: Kyle Gates; +Cc: Kenneth Johansson, linux-btrfs@vger.kernel.org
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
On Fri, Nov 02, 2012 at 10:54:47AM -0500, Kyle Gates wrote:
> > So I have ended up in a state where I can't delete files with rm.
> >
> > the error I get is no space on device. however I'm not even close to empty.
> > /dev/sdb1 38G 27G 9.5G 75%
> > there is about 800k files/dirs in this filesystem
> >
> > extra strange is that I can in another directory create and delete files.
> >
> > So I tried pretty much all I could google my way to but problem
> > persisted. So I decided to do a backup and a format. But when the backup
> > was done I tried one more time and now it was possible to delete the
> > directory and all content?
> >
> > using the 3.5 kernel in ubuntu 12.10. Is this a known issue ? is it
> > fixed in later kernels?
> >
> > fsck /btrfs scrub and kernel log. nothing indicate any problem of any kind.
> >
>
> First let's see the output of:
> btrfs fi df /mountpoint
>
> You're probably way over allocated in metadata so a balance should help:
> btrfs bal start -m /mountpoint
> or omit the -m option to run a full balance.
Or, better, -musage=5 (or 1), which will do even less work.
... but let's see the btrfs fi df output first. Could you also add the
output of "btrfs fi show" (no parameters), please?
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- You're never alone with a rubber duck... ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device.
2012-11-02 15:54 ` Kyle Gates
2012-11-02 15:59 ` Hugo Mills
@ 2012-11-06 13:23 ` Kenneth Johansson
1 sibling, 0 replies; 33+ messages in thread
From: Kenneth Johansson @ 2012-11-06 13:23 UTC (permalink / raw)
To: Kyle Gates; +Cc: linux-btrfs@vger.kernel.org
On 11/02/2012 04:54 PM, Kyle Gates wrote:
>> So I have ended up in a state where I can't delete files with rm.
>>
>> the error I get is no space on device. however I'm not even close to empty.
>> /dev/sdb1 38G 27G 9.5G 75%
>> there is about 800k files/dirs in this filesystem
>>
>> extra strange is that I can in another directory create and delete files.
>>
>> So I tried pretty much all I could google my way to but problem
>> persisted. So I decided to do a backup and a format. But when the backup
>> was done I tried one more time and now it was possible to delete the
>> directory and all content?
>>
>> using the 3.5 kernel in ubuntu 12.10. Is this a known issue ? is it
>> fixed in later kernels?
>>
>> fsck /btrfs scrub and kernel log. nothing indicate any problem of any kind.
>>
> First let's see the output of:
> btrfs fi df /mountpoint
>
> You're probably way over allocated in metadata so a balance should help:
> btrfs bal start -m /mountpoint
> or omit the -m option to run a full balance.
I had to use the disk for work so I could not be stuck in that situation
and thus had to nuke the disk.
maybe I can recreate the state I put back mostly the same data again
minus some stuff I did not really need.
So under what circumstance can this actually happen ? why could I
remove/add files in one directory and not another? its the same
partition. And also the filesystem was just a few days old and no
snapshots or anything, well I do use lzo compression but other than that
default values was used to create it.
^ permalink raw reply [flat|nested] 33+ messages in thread
* no space left on device
@ 2012-08-03 10:05 Mark Marshall
2012-08-04 9:14 ` Chris Samuel
2012-08-04 9:26 ` Martin Steigerwald
0 siblings, 2 replies; 33+ messages in thread
From: Mark Marshall @ 2012-08-03 10:05 UTC (permalink / raw)
To: linux-btrfs
Hi,
I am new to btrfs, and just installed a new system with SLED 11 SP2 a
few days ago.
However the system seems to be in a real sad state now, saying there
is no free space left on the device even though there is about 8GB
left on the / filesystem.
A defragment works sometimes but then it goes back to the original
state a day or two later. Other times the command just won't respond.
I've had this happen with 2-3 systems now, is there a solution? I
can't keep going around to users machines and defragmenting all the
time !
Thanks,
Mark
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2012-08-03 10:05 Mark Marshall
@ 2012-08-04 9:14 ` Chris Samuel
2012-08-04 9:26 ` Martin Steigerwald
1 sibling, 0 replies; 33+ messages in thread
From: Chris Samuel @ 2012-08-04 9:14 UTC (permalink / raw)
To: linux-btrfs; +Cc: markmarshall8
Hi Mark,
On 08/03/2012 08:05 PM, Mark Marshall wrote:
> I am new to btrfs, and just installed a new system with SLED 11 SP2 a
> few days ago.
Looking at the release notes for SLED11 SP2 it appears to ship with an
ancient kernel (in btrfs terms), 3.0.10. You will want to upgrade to
*at least* a 3.2.x kernel (I use Kubuntu 12.04 on my work laptop with
btrfs /home and had no issues with its 3.2.x), though it's likely you'll
want to go straight to the current 3.5.x kernel.
Best of luck!
Chris
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2012-08-03 10:05 Mark Marshall
2012-08-04 9:14 ` Chris Samuel
@ 2012-08-04 9:26 ` Martin Steigerwald
1 sibling, 0 replies; 33+ messages in thread
From: Martin Steigerwald @ 2012-08-04 9:26 UTC (permalink / raw)
To: linux-btrfs; +Cc: Mark Marshall
Am Freitag, 3. August 2012 schrieb Mark Marshall:
> Hi,
Hi Mark,
> I am new to btrfs, and just installed a new system with SLED 11 SP2 a
> few days ago.
Now you have a nice SLED 11 SP 2 with official BTRFS support from SUSE.
Did you consider to ask SUSE support? ;)
> However the system seems to be in a real sad state now, saying there
> is no free space left on the device even though there is about 8GB
> left on the / filesystem.
>
> A defragment works sometimes but then it goes back to the original
> state a day or two later. Other times the command just won't respond.
>
> I've had this happen with 2-3 systems now, is there a solution? I
> can't keep going around to users machines and defragmenting all the
> time !
First read and understand
https://btrfs.wiki.kernel.org/index.php/FAQ#Aaargh.21_My_filesystem_is_full.2C_and_I.27ve_put_almost_nothing_into_it.21
plus the following FAQs in there.
Then come back with more information.
Possible a btrfs balance will work to make some trees smaller, but this
depends on the current state of your BTRFS. The information you provided
is not nearly enough for an exact diagnosis. A defragment likely won´t
help tough.
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
^ permalink raw reply [flat|nested] 33+ messages in thread
* no space left on device
@ 2011-02-07 21:21 Leonidas Spyropoulos
2011-02-07 21:27 ` Erik Logtenberg
2011-02-08 0:09 ` C Anthony Risinger
0 siblings, 2 replies; 33+ messages in thread
From: Leonidas Spyropoulos @ 2011-02-07 21:21 UTC (permalink / raw)
To: linux-btrfs
Hey all,
I run into no space left on device on a virtualbox
After installing Debian 6 on a virtual machine
I tried installing the KDE desktop
The system HDD is 8Gb
Both root (/) and /home are btrfs
over LVM.
While installing the packages I run into:
no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_used, 0
bytes_reserved,
0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total
df shows only 74% used space on /
kernel used: stock debian 6 2.6.32-5-686
At the moment I cannot access it with normal boot, only recovery mode.
I can provide whatever info you would like as long as you think of a
way to load the normal system and not the recovery mode.
--
Caution: breathing may be hazardous to your health.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2011-02-07 21:21 Leonidas Spyropoulos
@ 2011-02-07 21:27 ` Erik Logtenberg
2011-02-07 23:58 ` Robert G.
2011-02-08 0:09 ` C Anthony Risinger
1 sibling, 1 reply; 33+ messages in thread
From: Erik Logtenberg @ 2011-02-07 21:27 UTC (permalink / raw)
Cc: linux-btrfs
Hi Leonidas,
Please check this:
btrfs fi df /home
If this shows much of your space used by metadata then please use:
btrfs fi balance /home
Note that this can take a long (>1 day) time to complete on a big FS.
- Erik
On 02/07/2011 10:21 PM, Leonidas Spyropoulos wrote:
> Hey all,
>
> I run into no space left on device on a virtualbox
>
> After installing Debian 6 on a virtual machine
> I tried installing the KDE desktop
>
> The system HDD is 8Gb
> Both root (/) and /home are btrfs
> over LVM.
>
> While installing the packages I run into:
>
> no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_used, 0
> bytes_reserved,
> 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total
>
> df shows only 74% used space on /
>
> kernel used: stock debian 6 2.6.32-5-686
>
> At the moment I cannot access it with normal boot, only recovery mode.
>
> I can provide whatever info you would like as long as you think of a
> way to load the normal system and not the recovery mode.
>
>
>
>
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2011-02-07 21:27 ` Erik Logtenberg
@ 2011-02-07 23:58 ` Robert G.
0 siblings, 0 replies; 33+ messages in thread
From: Robert G. @ 2011-02-07 23:58 UTC (permalink / raw)
To: Erik Logtenberg; +Cc: linux-btrfs
Hi,
I had a similar problem on my Debian (squeeze) about a half year ago.
I've described that on this mailing list. That was a main reason to
migrate from brtfs (-o ssd) to ext4.=20
I know it's a pain for my SSD but I want to revert this fail system
when it will be more stable. Thanks God it was added to Debian 6 and
Ubuntu 10.10. Now there will be even more alpha/beta testers.
And some problems will be noticed more frequently.
When will you change status from experimental to stable in the kernel?
Regards
Robert.
Dnia 2011-02-07, o godz. 22:27:14
Erik Logtenberg <erik@logtenberg.eu> napisa=C5=82(a):
> Hi Leonidas,
>=20
> Please check this:
>=20
> btrfs fi df /home
>=20
> If this shows much of your space used by metadata then please use:
>=20
> btrfs fi balance /home
>=20
> Note that this can take a long (>1 day) time to complete on a big FS.
>=20
> - Erik
>=20
>=20
>=20
> On 02/07/2011 10:21 PM, Leonidas Spyropoulos wrote:
> > Hey all,
> >=20
> > I run into no space left on device on a virtualbox
> >=20
> > After installing Debian 6 on a virtual machine
> > I tried installing the KDE desktop
> >=20
> > The system HDD is 8Gb
> > Both root (/) and /home are btrfs
> > over LVM.
> >=20
> > While installing the packages I run into:
> >=20
> > no space left, need 4096, 4096 dealloc bytes, 1776283648
> > bytes_used, 0 bytes_reserved,
> > 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total
> >=20
> > df shows only 74% used space on /
> >=20
> > kernel used: stock debian 6 2.6.32-5-686
> >=20
> > At the moment I cannot access it with normal boot, only recovery
> > mode.
> >=20
> > I can provide whatever info you would like as long as you think of =
a
> > way to load the normal system and not the recovery mode.
> >=20
> >=20
> >=20
> >=20
>=20
> --
> 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
--
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
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: no space left on device
2011-02-07 21:21 Leonidas Spyropoulos
2011-02-07 21:27 ` Erik Logtenberg
@ 2011-02-08 0:09 ` C Anthony Risinger
1 sibling, 0 replies; 33+ messages in thread
From: C Anthony Risinger @ 2011-02-08 0:09 UTC (permalink / raw)
To: Leonidas Spyropoulos; +Cc: linux-btrfs
On Mon, Feb 7, 2011 at 3:21 PM, Leonidas Spyropoulos
<artafinde@gmail.com> wrote:
> Hey all,
>
> I run into no space left on device on a virtualbox
>
> After installing Debian 6 on a virtual machine
> I tried installing the KDE desktop
>
> The system HDD is 8Gb
> Both root (/) and /home are btrfs
> over LVM.
>
> While installing the packages I run into:
>
> no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_used, 0
> bytes_reserved,
> 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total
>
> df shows only 74% used space on /
>
> kernel used: stock debian 6 2.6.32-5-686
>
> At the moment I cannot access it with normal boot, only recovery mode.
>
> I can provide whatever info you would like as long as you think of a
> way to load the normal system and not the recovery mode.
IIRC .32 has all sorts of ENOSPC problems; I think this was seriously
tackled in kernels > .32... this kernel was only declared ready for
"early adopters", with an "expect issues" disclaimer.
The btrfs-tools in squeeze is probably so old you may not even have
the `btrfs` binary, but I don't run debian so I'm not sure there...
not really a solution probably for you, but I wouldn't run that kernel
if using btrfs.
C Anthony
^ permalink raw reply [flat|nested] 33+ messages in thread
* no space left on device
@ 2010-07-30 5:31 Lubos Kolouch
[not found] ` <AANLkTikBRfR45DZxZW9LM6wnREWrbysPCr9Z1d3YuYhC@mail.gmail.com>
0 siblings, 1 reply; 33+ messages in thread
From: Lubos Kolouch @ 2010-07-30 5:31 UTC (permalink / raw)
To: linux-btrfs
Hello,
kerner 2.6.35-rc6
btrfs filesystem df /home
Data: total=1.68TB, used=987.62GB
Metadata: total=56.01GB, used=48.16GB
System: total=12.00MB, used=200.00KB
touch: cannot touch `/home/x': No space left on device
Any ideas what I should do?
Thank you
Lubos
^ permalink raw reply [flat|nested] 33+ messages in thread
* No space left on device
@ 2008-12-08 9:46 Gabor MICSKO
2008-12-08 14:02 ` dcg
0 siblings, 1 reply; 33+ messages in thread
From: Gabor MICSKO @ 2008-12-08 9:46 UTC (permalink / raw)
To: linux-btrfs
hi,
I have an 80GB external HDD with one btrfs partition. Latest kernel
module and btrfs-progs from "unstable" git repos.
# mount
[...]
/dev/sdb1 on /media/coolermaster type btrfs (rw)
# df -h
[...]
/dev/sdb1 75G 61G 15G 81% /media/coolermaster
It seems like i have 15GB free space on the btrfs formatted partition,
but when i try to create a file of 4GB on the btrfs filesystem i get the
following error:
root@alderaan:/media/coolermaster/tmp# dd if=/dev/zero of=foobar.img
bs=1024 count=4000K
dd: writing `foobar.img': No space left on device
3372894+0 records in
3372893+0 records out
3453842432 bytes (3.5 GB) copied, 321.087 s, 10.8 MB/s
syslog:
Dec 8 10:35:46 alderaan kernel: [30716.434747] device fsid
46489b7e62f254e0-e306291dd7724d8f devid 1 transid 283 /dev/sdb1
Dec 8 10:35:50 alderaan kernel: [30720.457774] space info full 36
Am i missing something (e.g. reserved space for root, etc.) obvious
here?
Thanks,
--
mg
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: No space left on device
2008-12-08 9:46 No " Gabor MICSKO
@ 2008-12-08 14:02 ` dcg
0 siblings, 0 replies; 33+ messages in thread
From: dcg @ 2008-12-08 14:02 UTC (permalink / raw)
To: Gabor MICSKO; +Cc: linux-btrfs
El Mon, 08 Dec 2008 10:46:25 +0100, Gabor MICSKO <gabor.micsko@gmail.co=
m> escribi=C3=B3:
> # df -h
> [...]
> /dev/sdb1 75G 61G 15G 81% /media/coolermaster
>=20
> It seems like i have 15GB free space on the btrfs formatted partition=
,
> but when i try to create a file of 4GB on the btrfs filesystem i get =
the
> following error:
btrfs has an (artificial) limit of 85% of the space which won't be lift=
ed until
the allocation code is mature. So you can't use the 100% for now...that
--
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
^ permalink raw reply [flat|nested] 33+ messages in thread
end of thread, other threads:[~2014-02-12 11:08 UTC | newest]
Thread overview: 33+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <AANLkTinH225vC8fRbA7zk_iOEmyADFZMBS6b7gx1tOxm@mail.gmail.com>
2011-02-08 9:00 ` no space left on device Leonidas Spyropoulos
2011-02-08 9:31 ` cwillu
2011-02-08 10:08 ` Leonidas Spyropoulos
2011-02-08 13:19 ` Helmut Hullen
2011-02-08 18:56 ` Erik Logtenberg
2011-02-08 19:43 ` Helmut Hullen
2011-02-12 14:11 ` Erik Logtenberg
2011-02-08 20:36 ` Helmut Hullen
2011-02-09 12:41 ` kernel panic (was: no space left on device) Helmut Hullen
2014-02-12 9:51 No space left on device Jakob Truelsen
2014-02-12 10:26 ` Hugo Mills
2014-02-12 10:45 ` Jakob Truelsen
2014-02-12 11:07 ` Hugo Mills
2014-02-12 10:34 ` Leonidas Spyropoulos
-- strict thread matches above, loose matches on Subject: below --
2012-11-01 13:35 no " Kenneth Johansson
2012-11-02 15:54 ` Kyle Gates
2012-11-02 15:59 ` Hugo Mills
2012-11-06 13:23 ` Kenneth Johansson
2012-08-03 10:05 Mark Marshall
2012-08-04 9:14 ` Chris Samuel
2012-08-04 9:26 ` Martin Steigerwald
2011-02-07 21:21 Leonidas Spyropoulos
2011-02-07 21:27 ` Erik Logtenberg
2011-02-07 23:58 ` Robert G.
2011-02-08 0:09 ` C Anthony Risinger
2010-07-30 5:31 Lubos Kolouch
[not found] ` <AANLkTikBRfR45DZxZW9LM6wnREWrbysPCr9Z1d3YuYhC@mail.gmail.com>
2010-07-30 12:27 ` Lubos Kolouch
[not found] ` <AANLkTinBj1O-LapAeBCT2Y3A1ZhfFZ3AotCk6SZ-e-2U@mail.gmail.com>
2010-07-30 14:30 ` Leonidas Spyropoulos
2010-07-30 15:02 ` Lubos Kolouch
2010-07-30 15:09 ` Lubos Kolouch
2010-08-14 20:15 ` Lubos Kolouch
2008-12-08 9:46 No " Gabor MICSKO
2008-12-08 14:02 ` dcg
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).