All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hendrik Friedel <hendrik@friedels.name>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: Chris Murphy <lists@colorremedies.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck does not fix
Date: Tue, 21 Jan 2014 21:01:56 +0100	[thread overview]
Message-ID: <52DED234.4060305@friedels.name> (raw)
In-Reply-To: <52DED1C2.60103@friedels.name>

Hello again:

> I think, I do/did have some symptoms, but I cannot exclude other reasons..
> -High Load without high cpu-usage (io was the bottleneck)
> -Just now: transfer from one directory to the other on the same
> subvolume (from /mnt/subvol/A/B to /mnt/subvol/A) I get 1.2MB/s instead
> of > 60.
> -For some of the files I even got a "no space left on device" error.

And the first symptom is also there:
top - 21:00:58 up 22:19,  5 users,  load average: 1.08, 1.15, 1.09
Tasks: 204 total,   1 running, 203 sleeping,   0 stopped,   0 zombie
Cpu(s):  1.5%us,  2.7%sy,  0.3%ni, 66.6%id, 28.6%wa,  0.3%hi,  0.0%si, 
0.0%st
Mem:   3795584k total,  3614088k used,   181496k free,   367820k buffers
Swap:  8293372k total,    45464k used,  8247908k free,  2337704k cached

Greetings,
Hendrik



-- 
Hendrik Friedel
Auf dem Brink 12
28844 Weyhe
Mobil 0178 1874363

  reply	other threads:[~2014-01-21 20:02 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 19:41 btrfsck does not fix Hendrik Friedel
2014-01-03 23:33 ` Chris Murphy
2014-01-04 21:21   ` Hendrik Friedel
2014-01-05 13:36     ` Hendrik Friedel
2014-01-05 16:55     ` Chris Murphy
2014-01-07 20:38       ` Hendrik Friedel
2014-01-10 23:53         ` Hendrik Friedel
2014-01-11  1:05           ` Chris Murphy
2014-01-12 22:31             ` Hendrik Friedel
2014-01-14  0:40               ` Chris Murphy
2014-01-14  6:03                 ` Duncan
2014-01-14  7:49                   ` Chris Murphy
2014-01-14  9:30                     ` Duncan
2014-01-14  9:38                       ` Hugo Mills
2014-01-14 17:17                       ` Chris Murphy
2014-01-18  7:20                         ` Chris Samuel
2014-01-14  8:16                 ` Hugo Mills
2014-01-19 19:37               ` Martin Steigerwald
2014-01-21 20:00                 ` Hendrik Friedel
2014-01-21 20:01                   ` Hendrik Friedel [this message]
2014-02-08 22:01                   ` Hendrik Friedel
2014-02-09  0:45                     ` Chris Murphy
2014-02-09  8:36                       ` Hendrik Friedel
2014-02-11  1:45                         ` Chris Murphy
2014-02-11  2:23                           ` Chris Murphy
2014-02-16 19:18                             ` Hendrik Friedel
2014-02-16 19:54                               ` Chris Murphy
2014-02-17  3:20                                 ` Duncan
2014-02-17  9:41                                   ` Goswin von Brederlow
2014-02-18 21:55                                   ` Hendrik Friedel
2014-02-18 22:12                                     ` Chris Murphy
2014-03-02 18:39                                       ` Hendrik Friedel
2014-03-03 22:35                                         ` Chris Murphy
2014-03-04  6:42                                           ` Hendrik Friedel
2014-03-04 17:02                                             ` Chris Murphy
2014-03-03  1:09                                 ` Russell Coker

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=52DED234.4060305@friedels.name \
    --to=hendrik@friedels.name \
    --cc=Martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.