From: Chris Mason <chris.mason@oracle.com>
To: "Florian D." <flockmock@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [ANNOUNCE] Btrfs: a copy on write, snapshotting FS
Date: Fri, 15 Jun 2007 15:11:53 -0400 [thread overview]
Message-ID: <20070615191153.GU2061@think.oraclecorp.com> (raw)
In-Reply-To: <4672E3B6.1030000@gmail.com>
On Fri, Jun 15, 2007 at 09:08:38PM +0200, Florian D. wrote:
> Chris Mason wrote:
> >
> >> is it possible to test it on top of LVM2 on RAID at this stage?
> >
> > Yes, I haven't done much multi-spindle testing yet, so I'm definitely
> > interested in these numbers.
> >
> > -chris
> >
> >
>
> I did not get very far:
>
>
> # insmod btrfs.ko
> # mkfs.btrfs /dev/brain_volume_group/btrfstest
> on close 0 blocks are allocated
> fs created on /dev/brain_volume_group/btrfstest blocksize 4096 blocks
> 4980736
>
> (/dev/brain_volume_group/btrfstest is a 20GB logical volume on top of
> RAID6)
>
> # mount /dev/brain_volume_group/btrfstest /mnt/temp/
> (this gives these kernel-msgs:
> [ 385.980358] btrfs: dm-6 checksum verify failed on 4
> [ 385.980462] btrfs: dm-6 checksum verify failed on 12
> [ 385.980559] btrfs: dm-6 checksum verify failed on 11
These are normal on the first mount, the mkfs doesn't set the csums on
the blocks it creates (will fix ;)
> )
>
> # touch /mnt/temp/default/testfile.txt
> [ 445.445638] btrfs: dm-6 checksum verify failed on 10
>
>
> # umount /mnt/temp/
>
> [ 457.980372] ------------[ cut here ]------------
> [ 457.980377] kernel BUG at fs/buffer.c:2644!
Whoops. Please try this:
diff -r 38b36aaaa731 disk-io.c
--- a/disk-io.c Fri Jun 15 13:50:20 2007 -0400
+++ b/disk-io.c Fri Jun 15 15:12:26 2007 -0400
@@ -541,6 +541,7 @@ int write_ctree_super(struct btrfs_trans
else
ret = submit_bh(WRITE, bh);
if (ret == -EOPNOTSUPP) {
+ lock_buffer(bh);
set_buffer_uptodate(bh);
root->fs_info->do_barriers = 0;
ret = submit_bh(WRITE, bh);
next prev parent reply other threads:[~2007-06-15 19:15 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 16:10 [ANNOUNCE] Btrfs: a copy on write, snapshotting FS Chris Mason
2007-06-12 19:53 ` Mike Snitzer
2007-06-12 20:14 ` Chris Mason
2007-06-13 3:08 ` Christoph Hellwig
2007-06-13 10:17 ` Chris Mason
2007-06-13 3:46 ` John Stoffel
2007-06-13 10:35 ` Chris Mason
2007-06-13 14:00 ` John Stoffel
2007-06-13 14:54 ` Chris Mason
2007-06-13 16:12 ` John Stoffel
2007-06-13 16:34 ` Chris Mason
2007-06-13 16:25 ` Grzegorz Kulewski
2007-06-14 18:20 ` Chuck Lever
2007-06-14 18:48 ` Chris Mason
2007-06-15 17:17 ` Chuck Lever
2007-06-14 18:29 ` Florian D.
2007-06-14 19:13 ` Chris Mason
2007-06-15 19:08 ` Florian D.
2007-06-15 19:11 ` Chris Mason [this message]
2007-06-15 20:46 ` Florian D.
2007-06-15 20:51 ` Chris Mason
2007-06-15 22:03 ` Florian D.
2007-06-16 0:54 ` Chris Mason
2007-06-16 9:31 ` Florian D.
2007-06-18 14:29 ` Chris Mason
2007-06-18 14:41 ` Chris Mason
2007-06-18 14:41 ` Chris Mason
2007-06-18 17:37 ` Vladislav Bolkhovitin
2007-06-18 20:08 ` John Stoffel
2007-06-19 9:11 ` Pádraig Brady
2007-06-19 10:01 ` Vladislav Bolkhovitin
2007-06-19 18:20 ` david
2007-06-20 8:41 ` Vladislav Bolkhovitin
2007-06-19 12:04 ` Chris Mason
2007-06-19 12:04 ` Chris Mason
2007-06-19 14:00 ` Vladislav Bolkhovitin
2007-06-19 14:00 ` Vladislav Bolkhovitin
2007-06-19 18:24 ` david
2007-06-19 18:28 ` Philipp Matthias Hahn
2007-06-19 18:28 ` Philipp Matthias Hahn
2007-06-20 8:44 ` Vladislav Bolkhovitin
2007-06-20 9:18 ` Ph. Marek
-- strict thread matches above, loose matches on Subject: below --
2007-06-13 5:45 Albert Cahalan
2007-06-13 12:00 ` Chris Mason
2007-06-13 16:14 ` Albert Cahalan
2007-06-13 16:57 ` Chris Mason
2007-06-14 6:59 ` Albert Cahalan
2007-06-14 12:30 ` 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=20070615191153.GU2061@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=flockmock@gmail.com \
--cc=linux-fsdevel@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.