From: Jim <jim@webstarts.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: ls hangs filesystem
Date: Tue, 18 Oct 2011 09:47:11 -0400 [thread overview]
Message-ID: <4E9D835F.1010706@webstarts.com> (raw)
In-Reply-To: <20111018133137.GB4276@localhost.localdomain>
I am on kernel 3.1.0-rc4. I am ssh'd into a remote machine so have no
access to keyboard, any other way to get the info you need? Thanks again.
Jim
On 10/18/2011 09:31 AM, Josef Bacik wrote:
> On Tue, Oct 18, 2011 at 09:25:46AM -0400, Jim wrote:
>> Good morning btrfs list,
>> I have been rsyncing files from an nfs mount to a btrfs filesystem.
>> After an rsync run I ls random subvols or directorys to check the
>> copy. About 60% to 70% of the time ls completely hangs. Ps aux
>> shows it as running but even when I let it go for up to an hour it
>> never finishes. Kill -9 will not stop the process. Dmesg shows
>> nothing beyond a successful mount at boot. I can't umount the
>> system because "filesystem is busy". I find that a forced reboot is
>> the only way to recapture the system. /var/log/messages has the
>> only indication (that I can find) that anything abnormal is
>> happening. A tail of the file is below. Thank you for any help and
>> advice.
> Hit sysrq+w when this happens and give us all the tracebacks. Also which kernel
> you are on would be helpful. Thanks,
>
> Josef
next prev parent reply other threads:[~2011-10-18 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 13:25 ls hangs filesystem Jim
2011-10-18 13:31 ` Josef Bacik
2011-10-18 13:47 ` Jim [this message]
2011-10-18 13:49 ` Sander
2011-10-18 13:50 ` Jim
2011-10-18 14:03 ` Jim
2011-10-18 14:04 ` Josef Bacik
2011-10-18 14:08 ` Jim
2011-10-18 14:09 ` Josef Bacik
2011-10-18 14:10 ` Jim
2011-10-18 14:26 ` Jim
2011-10-18 14:08 ` Sander
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=4E9D835F.1010706@webstarts.com \
--to=jim@webstarts.com \
--cc=josef@redhat.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