From: Fredrik Tolf <fredrik@dolda2000.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: Rebalancing RAID1
Date: Fri, 15 Feb 2013 04:50:23 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1302150447540.8810@shack.dolda2000.com> (raw)
In-Reply-To: <19ABBC76-F774-4225-87A4-73A4D546F53F@colorremedies.com>
On Thu, 14 Feb 2013, Chris Murphy wrote:
> Yeah he's getting a lot of these, and I don't know what it is:
>
>> Feb 14 08:32:30 nerv kernel: [180511.760850] lost page write due to I/O error on /dev/sdd1
>
> It's not tied to btrfs or libata so I don't think it's the drive itself
> reporting the write error.
Actually, it appears it might just be from btrfs:
> $ grep -rlI 'lost page write' /usr/local/src/linux-3.7.1/fs
> /usr/local/src/linux-3.7.1/fs/btrfs/disk-io.c
> /usr/local/src/linux-3.7.1/fs/buffer.c
And at btrfs/disk-io.c:2711 in this 3.7.1 source:
> printk_ratelimited_in_rcu(KERN_WARNING "lost page write due to "
> "I/O error on %s\n",
> rcu_str_deref(device->name));
So it's either from btrfs, or from the buffer cache, and seeing as how it
appears with other btrfs messages, I'd be willing to bet on the former. :)
--
Fredrik Tolf
next prev parent reply other threads:[~2013-02-15 3:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 23:01 Rebalancing RAID1 Fredrik Tolf
2013-02-13 0:58 ` Chris Murphy
2013-02-13 6:18 ` Fredrik Tolf
2013-02-13 8:10 ` Chris Murphy
2013-02-14 6:42 ` Fredrik Tolf
2013-02-14 7:27 ` Chris Murphy
2013-02-14 7:58 ` Fredrik Tolf
2013-02-14 8:41 ` Chris Murphy
2013-02-14 8:59 ` Hugo Mills
2013-02-14 18:05 ` Chris Murphy
2013-02-14 20:56 ` Hugo Mills
2013-02-14 22:11 ` Chris Murphy
2013-02-15 3:50 ` Fredrik Tolf [this message]
2013-02-15 3:55 ` Chris Murphy
2013-02-15 3:56 ` Fredrik Tolf
2013-02-15 4:03 ` Chris Murphy
2013-02-14 8:01 ` Chris Murphy
2013-02-15 4:06 ` Fredrik Tolf
2013-02-14 14:44 ` Martin Steigerwald
2013-02-14 18:45 ` Chris Murphy
2013-02-15 3:44 ` Fredrik Tolf
2013-02-15 5:49 ` Sander
2013-02-15 9:05 ` Martin Steigerwald
2013-02-15 21:56 ` Fredrik Tolf
2013-02-18 15:29 ` Stefan Behrens
2013-02-23 0:36 ` Fredrik Tolf
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=alpine.DEB.2.02.1302150447540.8810@shack.dolda2000.com \
--to=fredrik@dolda2000.com \
--cc=hugo@carfax.org.uk \
--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.