From: "Robert G." <ruppertus@o2.pl>
To: Erik Logtenberg <erik@logtenberg.eu>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: no space left on device
Date: Tue, 8 Feb 2011 00:58:49 +0100 [thread overview]
Message-ID: <20110208005849.10464462@leni> (raw)
In-Reply-To: <4D5063B2.4070609@logtenberg.eu>
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
next prev parent reply other threads:[~2011-02-07 23:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 21:21 no space left on device Leonidas Spyropoulos
2011-02-07 21:27 ` Erik Logtenberg
2011-02-07 23:58 ` Robert G. [this message]
2011-02-08 0:09 ` C Anthony Risinger
-- strict thread matches above, loose matches on Subject: below --
2014-02-12 9:51 No " 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
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
[not found] <AANLkTinH225vC8fRbA7zk_iOEmyADFZMBS6b7gx1tOxm@mail.gmail.com>
2011-02-08 9:00 ` 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
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
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=20110208005849.10464462@leni \
--to=ruppertus@o2.pl \
--cc=erik@logtenberg.eu \
--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).