From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs day 1
Date: Thu, 14 Aug 2008 00:11:20 -0700 [thread overview]
Message-ID: <20080814001120.4f1fea7a@speedy> (raw)
Setup new 60G home partition on laptop as a real life test of 0.16.
Using Ubuntu standard kernel 2.6.24-19-generic on i386
I notice that during normal (busy time) everything seems fine, but after going away
for a while and coming back, it seems sluggish. Lots of errors in log:
btrfs csum failed ino 139988 off 4583424 csum 3821684403 private 0
btrfs csum failed ino 139988 off 4579328 csum 3233603900 private 0
btrfs csum failed ino 139988 off 4575232 csum 306171610 private 0
Maybe it isn't handleing spindown properly? or something like that?
next reply other threads:[~2008-08-14 7:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 7:11 Stephen Hemminger [this message]
2008-08-14 10:25 ` btrfs day 1 Chris Mason
2008-08-14 16:19 ` Stephen Hemminger
2008-08-14 17:26 ` Chris Mason
2008-08-14 18:06 ` Stephen Hemminger
2008-08-14 18:21 ` Chris Mason
2008-08-14 18:27 ` Stephen Hemminger
2008-08-16 18:18 ` Chris Mason
2008-08-20 13:47 ` Chris Mason
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=20080814001120.4f1fea7a@speedy \
--to=stephen.hemminger@vyatta.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