From: Lubos Kolouch <lubos.kolouch@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: no space left on device
Date: Fri, 30 Jul 2010 15:02:18 +0000 (UTC) [thread overview]
Message-ID: <i2uphq$p75$1@dough.gmane.org> (raw)
In-Reply-To: AANLkTimcgzp8Fs524GMzPaancXZU689twnBH3orY0yYn@mail.gmail.com
With 2.6.34 it basically "works", but time to time the load goes up to =
50
and lot of btrfs-cleaner processess are spawned...=20
the system is responsive though, except for the filesystem... after an=20
hour or so the processes finish and the load goes back to normal
Lubos
> On Fri, Jul 30, 2010 at 3:26 PM, Leonidas Spyropoulos
> <artafinde@gmail.com> wrote:
>> I use the latest btrfs-tools and 2.6.34-020634-generic kernel for
>> lucid. Got no issues like that, is it happening with 2.6.34 kernel a=
s
>> well?
>>
>> On Fri, Jul 30, 2010 at 1:27 PM, Lubos Kolouch
>> <lubos.kolouch@gmail.com> wrote:
>>>
>>> Yes, I pulled today's btrfs-progs.
>>>
>>> Lubos
>>>
>>> On P=C3=A1, =C4=8Dec 30, 2010, 13:03:10, Leonidas Spyropoulos wrote=
:
>>> > Have you updated with latest btrfs-tools?
>>> >
>>> > On Fri, Jul 30, 2010 at 6:31 AM, Lubos Kolouch
>>> > <lubos.kolouch@gmail.com>wrote:
>>> >
>>> > > Hello,
>>> > >
>>> > > kerner 2.6.35-rc6
>>> > >
>>> > > btrfs filesystem df /home
>>> > > Data: total=3D1.68TB, used=3D987.62GB
>>> > > Metadata: total=3D56.01GB, used=3D48.16GB System: total=3D12.00=
MB,
>>> > > used=3D200.00KB
>>> > >
>>> > > touch: cannot touch `/home/x': No space left on device
>>> > >
>>> > > Any ideas what I should do?
>>> > >
>>> > > Thank you
>>> > >
>>> > > Lubos
>>> > >
--
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:[~2010-07-30 15:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 5:31 no space left on device 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 [this message]
2010-07-30 15:09 ` Lubos Kolouch
2010-08-14 20:15 ` Lubos Kolouch
-- 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
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
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='i2uphq$p75$1@dough.gmane.org' \
--to=lubos.kolouch@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).