From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs day 1
Date: Thu, 14 Aug 2008 09:19:37 -0700 [thread overview]
Message-ID: <20080814091937.470f42ed@speedy> (raw)
In-Reply-To: <1218709514.15342.370.camel@think.oraclecorp.com>
On Thu, 14 Aug 2008 06:25:14 -0400
Chris Mason <chris.mason@oracle.com> wrote:
> On Thu, 2008-08-14 at 00:11 -0700, Stephen Hemminger wrote:
> > 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
> >
>
> Thanks for giving things a try
>
> > 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?
>
> Were these the only errors in the log, or did you have other errors
> about not being able to find specific csums?
>
> What does 'going away for a while and coming back' include?
1. Start kernel build
2. Come back 2+ hrs later
(So problem could be in step 1 or 2)
All failures are on the same inode
next prev parent reply other threads:[~2008-08-14 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 7:11 btrfs day 1 Stephen Hemminger
2008-08-14 10:25 ` Chris Mason
2008-08-14 16:19 ` Stephen Hemminger [this message]
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=20080814091937.470f42ed@speedy \
--to=stephen.hemminger@vyatta.com \
--cc=chris.mason@oracle.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 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.