From: Diego Calleja <diegocg@gmail.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: WARNING in -rc3-00023-g14c62e7
Date: Sun, 28 Aug 2011 01:40:24 +0200 [thread overview]
Message-ID: <201108280140.25014.diegocg@gmail.com> (raw)
In-Reply-To: <201108270033.51177.diegocg@gmail.com>
On S=E1bado, 27 de Agosto de 2011 00:33:51 Diego Calleja escribi=F3:
> On Viernes, 26 de Agosto de 2011 22:59:54 Mitch Harder escribi=F3:
> >=20
> > Do you have autodefrag enabled?
>=20
> Yes
It seems that this problem has already been solved by Konstantin
Khlebnikov, he posted a patch on 17 August
[PATCH] btrfs: fix warning in iput for bad-inode
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-08-27 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 19:17 WARNING in -rc3-00023-g14c62e7 Diego Calleja
2011-08-26 20:59 ` Mitch Harder
2011-08-26 22:33 ` Diego Calleja
2011-08-27 23:40 ` Diego Calleja [this message]
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=201108280140.25014.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.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;
as well as URLs for NNTP newsgroup(s).