From: Yan Zheng <zheng.yan@oracle.com>
To: devzero@web.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs filesystem freeze
Date: Sun, 21 Dec 2008 19:13:19 +0800 [thread overview]
Message-ID: <494E24CF.9080907@oracle.com> (raw)
In-Reply-To: <550569572@web.de>
devzero@web.de wrote:
> Hello,
>
> i was testing btrfs a little bit for stability and i think i have found an issue.
>
> during some heavy activity (multiple processes writing/reading to compressed /btrfs at the same time), i did some snapshots in a loop (every 10 seconds).
>
> very soon, all filesystem activity stopped, i.e. i cannot read/write anyting from/to /btrfs anymore.
> this happens with latest git-unstable with kernel 2.6.27
> nothing in dmesg.
>
> besides that, the system seems ok.
>
> as the system is a vmware virtual machine, i did a snapshot of the system state, so we can always go back to this state.
>
> if somebody want`s to analyse this, please tell me what to do.
>
Thank you for reporting this. Please try the attached patch.
Yan Zheng
---
diff -urp 1/fs/btrfs/transaction.c 2/fs/btrfs/transaction.c
--- 1/fs/btrfs/transaction.c 2008-12-13 12:35:29.487886730 +0800
+++ 2/fs/btrfs/transaction.c 2008-12-21 19:09:09.000000000 +0800
@@ -804,7 +804,7 @@ static noinline int finish_pending_snaps
parent_inode = pending->dentry->d_parent->d_inode;
parent_root = BTRFS_I(parent_inode)->root;
- trans = btrfs_start_transaction(parent_root, 1);
+ trans = btrfs_join_transaction(parent_root, 1);
/*
* insert the directory item
next prev parent reply other threads:[~2008-12-21 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 23:26 btrfs filesystem freeze devzero
2008-12-21 11:13 ` Yan Zheng [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-21 14:09 devzero
2008-12-22 0:55 ` Yan Zheng
2009-01-05 15:44 ` Chris Mason
2009-01-05 21:14 ` Yan Zheng
2009-01-05 21:24 ` Chris Mason
2008-12-23 0:26 devzero
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=494E24CF.9080907@oracle.com \
--to=zheng.yan@oracle.com \
--cc=devzero@web.de \
--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