From: Michael Raskin <a0091f122@rambler.ru>
To: Chris Mason <chris.mason@oracle.com>,
Michael Raskin <a0091f122@rambler.ru>,
linux-btrfs@vger.kernel.org
Subject: Re: Btrfs warnings: -rc2
Date: Fri, 17 Jul 2009 00:32:28 +0400 [thread overview]
Message-ID: <4A5F8E5C.4050904@rambler.ru> (raw)
In-Reply-To: <20090716183250.GC3883@think>
Chris Mason wrote:
>
> 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
4873317 -rw-r--r-- 1 root root 0 Jul 17 00:29 foo
dmesg is clean
creating/deleting 2 files gives the same result (with even larger inodes
each time, although foo is deleted already). The same for ghost files.
dmesg is clean.
prev parent reply other threads:[~2009-07-16 20: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
2009-07-16 20:32 ` Michael Raskin [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=4A5F8E5C.4050904@rambler.ru \
--to=a0091f122@rambler.ru \
--cc=chris.mason@oracle.com \
--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