public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lee Trager" <lt73@cs.drexel.edu>
To: jim owens <jowens@hp.com>
Cc: Lee Trager <lt73@cs.drexel.edu>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Backport for 2.6.27 and 2.6.26 on the experimental branch
Date: Tue, 24 Feb 2009 15:36:29 -0500	[thread overview]
Message-ID: <20090224203629.GB12209@tux64-01> (raw)
In-Reply-To: <49A41F26.2020202@hp.com>

I ran a few tests that Jim suggested and found that btrfs works fine on
2.6.26 as long as there are only 23 or less files on the file system.
Anymore and I experience the lockup. Jim and I will be working to find a
solution but if anyone else has any clues that would be greatly
appreciated.

Lee
On Tue, Feb 24, 2009 at 11:24:06AM -0500, jim owens wrote:
> Lee Trager wrote:
>> The more and more I look at this problem the more I tend to think that
>> the issue is because of some change in the way the VFS or something
>> interacts with the file system. Does anyone know of any big changes? Why
>> is the inode being marked dirty? Is there some kind of read error. I'm
>> completly lost in solving this problem.
>
> Being a filesystem guy, I always try blaming vm or drivers :)
>
> Until someone with real experience gives us the answer,
> I'll work with you off the mailing list to try to narrow
> down why this is happening.
>
> jim

  reply	other threads:[~2009-02-24 20:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 17:45 [PATCH] Backport for 2.6.27 and 2.6.26 on the experimental branch Lee Trager
2009-02-20 18:25 ` jim owens
2009-02-23 22:23   ` Lee Trager
2009-02-24 16:24     ` jim owens
2009-02-24 20:36       ` Lee Trager [this message]
2009-02-25 23:09         ` Lee Trager

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=20090224203629.GB12209@tux64-01 \
    --to=lt73@cs.drexel.edu \
    --cc=jowens@hp.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