From: Josef Bacik <jbacik@fusionio.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: Josef Bacik <JBacik@fusionio.com>,
Chris Mason <clmason@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: No space left on device (28)
Date: Mon, 25 Mar 2013 16:14:26 -0400 [thread overview]
Message-ID: <20130325201426.GG1955@localhost.localdomain> (raw)
In-Reply-To: <514CC52B.1000201@profihost.ag>
On Fri, Mar 22, 2013 at 02:55:07PM -0600, Stefan Priebe wrote:
> Hi Jsoef,
>
> thanks!
Ok I don't think the thing I just fixed will make any difference for you so
here's another debug patch, just apply it on top of what I've already sent you
and re-run and give me the dmesg again. Thanks,
Josef
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index aabaea6..bf6433f 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -4162,7 +4162,11 @@ out:
}
if (flushing) {
if (ret == -ENOSPC) {
- printk(KERN_ERR "returning enospc, dumping space info\n");
+ spin_lock(&block_rsv->lock);
+ printk(KERN_ERR "returning enospc, space_info %u, size %Lu reserved %Lu, "
+ "flush %d, flush_state %d dumping space info\n", block_rsv->type,
+ block_rsv->size, block_rsv->reserved, flush, flush_state);
+ spin_unlock(&block_rsv->lock);
dump_space_info(space_info, 0, 0);
}
--
1.7.7.6
next prev parent reply other threads:[~2013-03-25 20:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 8:03 No space left on device (28) Stefan Priebe - Profihost AG
2013-03-21 18:00 ` Chris Mason
2013-03-21 18:35 ` Stefan Priebe - Profihost AG
2013-03-21 19:02 ` Chris Mason
2013-03-21 19:42 ` Stefan Priebe
2013-03-22 6:08 ` Stefan Priebe - Profihost AG
2013-03-22 12:11 ` Stefan Priebe - Profihost AG
2013-03-22 13:53 ` Josef Bacik
2013-03-22 13:56 ` Stefan Priebe - Profihost AG
2013-03-22 15:54 ` Josef Bacik
2013-03-22 19:10 ` Stefan Priebe
2013-03-22 20:49 ` Josef Bacik
2013-03-22 20:55 ` Stefan Priebe
2013-03-25 20:14 ` Josef Bacik [this message]
2013-03-26 7:45 ` Stefan Priebe
2013-03-26 12:53 ` Josef Bacik
2013-03-26 12:55 ` Stefan Priebe - Profihost AG
2013-03-26 13:30 ` Josef Bacik
2013-03-26 13:49 ` Stefan Priebe - Profihost AG
2013-03-26 14:44 ` Josef Bacik
2013-03-26 15:03 ` Stefan Priebe - Profihost AG
2013-03-26 15:25 ` Josef Bacik
2013-03-26 16:19 ` Stefan Priebe
2013-03-26 17:45 ` Josef Bacik
2013-03-26 19:05 ` Stefan Priebe
2013-03-26 19:16 ` Josef Bacik
2013-03-26 19:22 ` Stefan Priebe
2013-03-26 19:38 ` Josef Bacik
2013-03-26 19:47 ` Stefan Priebe
2013-03-22 6:13 ` Roman Mamedov
2013-03-22 6:24 ` cwillu
2013-03-22 6:39 ` Stefan Priebe - Profihost AG
2013-03-22 6:41 ` cwillu
2013-03-22 7:06 ` Stefan Priebe - Profihost AG
2013-03-22 6:38 ` Stefan Priebe - Profihost AG
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=20130325201426.GG1955@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=clmason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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