From: "Yan Zheng" <yanzheng@21cn.com>
To: "Christian Hesse" <mail@earthworm.de>
Cc: "Chris mason" <chris.mason@oracle.com>,
btrfs-devel@oss.oracle.com, linux-fsdevel@vger.kernel.org
Subject: Re: [Btrfs-devel] [ANNOUNCE] Btrfs v0.10 (online growing/shrinking, ext3 conversion, and more)
Date: Mon, 21 Jan 2008 17:15:32 +0800 [thread overview]
Message-ID: <3d0408630801210115j39c4b238ia1146f55aa046807@mail.gmail.com> (raw)
In-Reply-To: <200801210957.06927.mail@earthworm.de>
2008/1/21, Christian Hesse <mail@earthworm.de>:
> Back in early december I reported the problem for btrfs 0.9. Seems like the
> lockfs call still is not implemented. Any hints what I need when I try to
> code it myself?
Please try this dirty patch. I think it can solve your problem.
Regards
YZ
---
diff -r ac53d7df4c11 super.c
--- a/super.c Thu Jan 17 12:58:00 2008 -0500
+++ b/super.c Mon Jan 21 17:10:00 2008 +0800
@@ -423,6 +423,18 @@ static struct file_system_type btrfs_fs_
.fs_flags = FS_REQUIRES_DEV,
};
+static void btrfs_write_super_lockfs(struct super_block *sb)
+{
+ struct btrfs_root *root = btrfs_sb(sb);
+ btrfs_transaction_flush_work(root);
+}
+
+static void btrfs_unlockfs(struct super_block *sb)
+{
+ struct btrfs_root *root = btrfs_sb(sb);
+ btrfs_transaction_queue_work(root, HZ * 30);
+}
+
static struct super_operations btrfs_super_ops = {
.delete_inode = btrfs_delete_inode,
.put_inode = btrfs_put_inode,
@@ -435,6 +447,8 @@ static struct super_operations btrfs_sup
.alloc_inode = btrfs_alloc_inode,
.destroy_inode = btrfs_destroy_inode,
.statfs = btrfs_statfs,
+ .write_super_lockfs = btrfs_write_super_lockfs,
+ .unlockfs = btrfs_unlockfs,
};
static int __init init_btrfs_fs(void)
next prev parent reply other threads:[~2008-01-21 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 15:52 [ANNOUNCE] Btrfs v0.10 (online growing/shrinking, ext3 conversion, and more) Chris Mason
2008-01-15 16:55 ` Kyle McMartin
2008-01-16 10:02 ` [Btrfs-devel] " Christian Hesse
2008-01-16 17:50 ` Simon Holm Thøgersen
2008-01-17 18:25 ` Chris mason
2008-01-17 19:28 ` Daniel Phillips
2008-01-17 20:14 ` Chris mason
2008-01-17 23:17 ` Christian Hesse
2008-01-18 13:48 ` Chris mason
2008-01-21 8:57 ` Christian Hesse
2008-01-21 9:15 ` Yan Zheng [this message]
2008-01-21 10:32 ` Christian Hesse
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=3d0408630801210115j39c4b238ia1146f55aa046807@mail.gmail.com \
--to=yanzheng@21cn.com \
--cc=btrfs-devel@oss.oracle.com \
--cc=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mail@earthworm.de \
/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;
as well as URLs for NNTP newsgroup(s).