public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Trager <lt73@cs.drexel.edu>
To: Btrfs Development List <linux-btrfs@vger.kernel.org>
Subject: btrfs lockup after mounting for a second time on 2.6.26
Date: Thu, 12 Feb 2009 01:31:24 -0500	[thread overview]
Message-ID: <4993C23C.8000108@cs.drexel.edu> (raw)

While running a few tests with the btrfs sources pulled from
btrfs-unstable patched with my patch to compile under 2.6.26 I
encountered a very weird problem. Everything works fine the first time I
mount the file system (either actual disk or loop back). When I
unmounted the file system and mounted it again(I'm not doing mount -o
remount ...) btrfs is completely unusable. When I tried to view some of
the data which I previously put on the btrfs partition by doing a simple
ls /mnt/btrfs in bash nothing happens. ls shows nothing, just hangs, and
I am unable to kill ls. The same thing happens when I try to copy a file
from my ext3 partition onto the btrfs partition after mounting it for a
second time. The rest of the system is completely usable and the only
things that are effects are applications which are trying to read/write
from the btrfs file system. There are no kernel opps or any other errors
messages in any of my logs. This happens if I have compression on or
not. I'd be happy to fix this issue but I don't have a clue about where
to start looking for what is wrong.

Could someone please help me?

Thanks,

Lee


             reply	other threads:[~2009-02-12  6:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12  6:31 Lee Trager [this message]
2009-02-12 14:51 ` btrfs lockup after mounting for a second time on 2.6.26 Chris Mason
2009-02-12 16:57   ` Lee Trager
2009-02-12 17:08   ` Lee Trager
2009-02-18 20:51   ` 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=4993C23C.8000108@cs.drexel.edu \
    --to=lt73@cs.drexel.edu \
    --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