From: Filipe Manana <fdmanana@kernel.org> To: Oliver Sang <oliver.sang@intel.com> Cc: 0day robot <lkp@intel.com>, LKML <linux-kernel@vger.kernel.org>, linux-btrfs <linux-btrfs@vger.kernel.org>, lkp@lists.01.org Subject: Re: [btrfs] 62bd8124e2: WARNING:at_fs/btrfs/block-rsv.c:#btrfs_release_global_block_rsv[btrfs] Date: Fri, 17 Jun 2022 11:32:44 +0100 [thread overview] Message-ID: <20220617103244.GA4042635@falcondesktop> (raw) In-Reply-To: <20220616024204.GA25633@xsang-OptiPlex-9020> On Thu, Jun 16, 2022 at 10:42:04AM +0800, Oliver Sang wrote: > hi, Filipe Manana, > > On Mon, Jun 13, 2022 at 11:50:05AM +0100, Filipe Manana wrote: > > > > Thanks for running the test again Oliver. > > Running the fxmark test on my machines, I can't trigger anything. > > > > May I ask you to run again the test but with the attached debug patch > > on top of it? > > I reran the test by applied your patch upon 62bd8124e2. one dmesg is attached. > > not sure if it supplies enough information? we need some extra effort to > enable below ftrace in our auto-test framework. so if dmesg is good enough, > please let us know, then we can save some efforts :) Thanks a lot! Thanks Oliver. In the meanwhile I found a way to reproduce the issue with a test case from fstests, so I now have everything I need to debug and fix the issue. Thanks! > > > > > Also, if possible, with ftrace enabled like this: > > > > modprobe btrfs > > echo 0 > /sys/kernel/debug/tracing/tracing_on > > echo > /sys/kernel/debug/tracing/trace > > echo $((1 << 24)) > /sys/kernel/debug/tracing/buffer_size_kb > > echo nop > /sys/kernel/debug/tracing/current_tracer > > echo 1 > /sys/kernel/tracing/events/btrfs/btrfs_space_reservation/enable > > > > echo 1 > /sys/kernel/debug/tracing/tracing_on > > > > <run the test> > > > > echo 0 > /sys/kernel/debug/tracing/tracing_on > > > > Then collect the trace to a file and send it over to me: > > > > cat /sys/kernel/debug/tracing/trace | xz -9 > trace.txt.xz > > > > And of course, the dmesg result as well. > > > > Thanks! > > > > > > > > > > > > > >
WARNING: multiple messages have this Message-ID (diff)
From: Filipe Manana <fdmanana@kernel.org> To: lkp@lists.01.org Subject: Re: [btrfs] 62bd8124e2: WARNING:at_fs/btrfs/block-rsv.c:#btrfs_release_global_block_rsv[btrfs] Date: Fri, 17 Jun 2022 11:32:44 +0100 [thread overview] Message-ID: <20220617103244.GA4042635@falcondesktop> (raw) In-Reply-To: <20220616024204.GA25633@xsang-OptiPlex-9020> [-- Attachment #1: Type: text/plain, Size: 1649 bytes --] On Thu, Jun 16, 2022 at 10:42:04AM +0800, Oliver Sang wrote: > hi, Filipe Manana, > > On Mon, Jun 13, 2022 at 11:50:05AM +0100, Filipe Manana wrote: > > > > Thanks for running the test again Oliver. > > Running the fxmark test on my machines, I can't trigger anything. > > > > May I ask you to run again the test but with the attached debug patch > > on top of it? > > I reran the test by applied your patch upon 62bd8124e2. one dmesg is attached. > > not sure if it supplies enough information? we need some extra effort to > enable below ftrace in our auto-test framework. so if dmesg is good enough, > please let us know, then we can save some efforts :) Thanks a lot! Thanks Oliver. In the meanwhile I found a way to reproduce the issue with a test case from fstests, so I now have everything I need to debug and fix the issue. Thanks! > > > > > Also, if possible, with ftrace enabled like this: > > > > modprobe btrfs > > echo 0 > /sys/kernel/debug/tracing/tracing_on > > echo > /sys/kernel/debug/tracing/trace > > echo $((1 << 24)) > /sys/kernel/debug/tracing/buffer_size_kb > > echo nop > /sys/kernel/debug/tracing/current_tracer > > echo 1 > /sys/kernel/tracing/events/btrfs/btrfs_space_reservation/enable > > > > echo 1 > /sys/kernel/debug/tracing/tracing_on > > > > <run the test> > > > > echo 0 > /sys/kernel/debug/tracing/tracing_on > > > > Then collect the trace to a file and send it over to me: > > > > cat /sys/kernel/debug/tracing/trace | xz -9 > trace.txt.xz > > > > And of course, the dmesg result as well. > > > > Thanks! > > > > > > > > > > > > > >
next prev parent reply other threads:[~2022-06-17 10:32 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-31 15:06 [PATCH 00/12] btrfs: some improvements and cleanups around delayed items fdmanana 2022-05-31 15:06 ` [PATCH 01/12] btrfs: balance btree dirty pages and delayed items after a rename fdmanana 2022-05-31 15:16 ` Nikolay Borisov 2022-05-31 23:13 ` Anand Jain 2022-05-31 15:06 ` [PATCH 02/12] btrfs: free the path earlier when creating a new inode fdmanana 2022-05-31 15:21 ` Nikolay Borisov 2022-05-31 23:22 ` Anand Jain 2022-06-01 9:34 ` Filipe Manana 2022-06-01 11:11 ` Anand Jain 2022-06-01 11:51 ` David Sterba 2022-05-31 15:06 ` [PATCH 03/12] btrfs: balance btree dirty pages and delayed items after clone and dedupe fdmanana 2022-06-01 0:54 ` Anand Jain 2022-05-31 15:06 ` [PATCH 04/12] btrfs: add assertions when deleting batches of delayed items fdmanana 2022-06-01 1:34 ` Anand Jain 2022-05-31 15:06 ` [PATCH 05/12] btrfs: deal with deletion errors when deleting " fdmanana 2022-06-01 1:44 ` Anand Jain 2022-05-31 15:06 ` [PATCH 06/12] btrfs: refactor the delayed item deletion entry point fdmanana 2022-05-31 15:06 ` [PATCH 07/12] btrfs: improve batch deletion of delayed dir index items fdmanana 2022-06-02 8:24 ` Nikolay Borisov 2022-06-02 8:55 ` Filipe Manana 2022-05-31 15:06 ` [PATCH 08/12] btrfs: assert that delayed item is a dir index item when adding it fdmanana 2022-05-31 15:06 ` [PATCH 09/12] btrfs: improve batch insertion of delayed dir index items fdmanana 2022-05-31 15:06 ` [PATCH 10/12] btrfs: do not BUG_ON() on failure to reserve metadata for delayed item fdmanana 2022-05-31 15:06 ` [PATCH 11/12] btrfs: set delayed item type when initializing it fdmanana 2022-05-31 15:06 ` [PATCH 12/12] btrfs: reduce amount of reserved metadata for delayed item insertion fdmanana 2022-06-08 15:23 ` [btrfs] 62bd8124e2: WARNING:at_fs/btrfs/block-rsv.c:#btrfs_release_global_block_rsv[btrfs] kernel test robot 2022-06-08 15:23 ` kernel test robot 2022-06-09 9:46 ` Filipe Manana 2022-06-09 9:46 ` Filipe Manana 2022-06-10 1:26 ` Oliver Sang 2022-06-10 1:26 ` Oliver Sang 2022-06-12 14:36 ` Oliver Sang 2022-06-12 14:36 ` Oliver Sang 2022-06-13 10:50 ` Filipe Manana 2022-06-13 10:50 ` Filipe Manana 2022-06-16 2:42 ` Oliver Sang 2022-06-16 2:42 ` Oliver Sang 2022-06-17 10:32 ` Filipe Manana [this message] 2022-06-17 10:32 ` Filipe Manana 2022-06-01 18:35 ` [PATCH 00/12] btrfs: some improvements and cleanups around delayed items David Sterba 2022-06-02 9:34 ` Nikolay Borisov
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=20220617103244.GA4042635@falcondesktop \ --to=fdmanana@kernel.org \ --cc=linux-btrfs@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lkp@intel.com \ --cc=lkp@lists.01.org \ --cc=oliver.sang@intel.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: linkBe 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.