From: Chris Mason <chris.mason@oracle.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Stephen Hemminger <stephen.hemminger@vyatta.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs day 1
Date: Thu, 14 Aug 2008 14:21:22 -0400 [thread overview]
Message-ID: <1218738082.15342.388.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20080814110612.1f411564@extreme>
On Thu, 2008-08-14 at 11:06 -0700, Stephen Hemminger wrote:
> > So, the question is why the kernel compile workload works for me. What
> > kind of hardware are you running (ram, cpu, disks?)
>
> Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz
> Memory 2G
> Disk 80G (partition was 20G)
>
It seems you have the secret to corrupting things. I'll try to
reproduce with smaller partitions and less ram here.
-chris
next prev parent reply other threads:[~2008-08-14 18:21 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
2008-08-14 17:26 ` Chris Mason
2008-08-14 18:06 ` Stephen Hemminger
2008-08-14 18:21 ` Chris Mason [this message]
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=1218738082.15342.388.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=stephen.hemminger@vyatta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox