From: Chris Mason <chris.mason@oracle.com>
To: Michael Raskin <a0091f122@rambler.ru>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs warnings: -rc2
Date: Thu, 16 Jul 2009 14:32:50 -0400 [thread overview]
Message-ID: <20090716183250.GC3883@think> (raw)
In-Reply-To: <4A5F3AD9.5040005@rambler.ru>
On Thu, Jul 16, 2009 at 06:36:09PM +0400, Michael Raskin wrote:
> I checked the same usage scenario with -rc2 kernel..
>
> Looks like it is just because of allmodconfig. Interesting fact,
> though: now warnings are thrown on on-disk operations, errors are on
> rbtree operations.
Could you please touch foo ; ls -lai foo and send us the results. Yan
Zheng has a theory that it is related to inode numbers
-chris
next prev parent reply other threads:[~2009-07-16 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 14:36 Btrfs warnings: -rc2 Michael Raskin
2009-07-16 18:32 ` Chris Mason [this message]
2009-07-16 20:32 ` Michael Raskin
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=20090716183250.GC3883@think \
--to=chris.mason@oracle.com \
--cc=a0091f122@rambler.ru \
--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