From: Eric Sandeen <sandeen-+82itfer+wXR7s880joybQ@public.gmane.org>
To: Alexander Beregalov
<a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org
Subject: Re: 2.6.30-rc4: xfs_fsr hangs
Date: Thu, 07 May 2009 18:55:47 -0500 [thread overview]
Message-ID: <4A037503.1070904@sandeen.net> (raw)
In-Reply-To: <4A036FBC.9020201-+82itfer+wXR7s880joybQ@public.gmane.org>
Eric Sandeen wrote:
> there are 2 subsequent unlocks for the same inode:
>
> 1:
> xfs_iunlock: ip ca2304c0 ino 132 flags 0x5
...
> 2:
> xfs_iunlock: ip ca230980 ino 131 flags 0x5
Ugh no, those are 2 different inodes.... I can read, really. :) still,
looking into it.
-Eric
next prev parent reply other threads:[~2009-05-07 23:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 20:33 2.6.30-rc4: xfs_fsr hangs Alexander Beregalov
[not found] ` <a4423d670905011333s664115bdh1d72392897567c1d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-02 10:14 ` Heinz Diehl
[not found] ` <20090502101405.GA6145-HjJ2MNWy62to6+H+lsi3Gti2O/JbrIOy@public.gmane.org>
2009-05-02 18:35 ` Alexander Beregalov
2009-05-02 18:56 ` Eric Sandeen
[not found] ` <49FC9762.6010109-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-02 18:59 ` Alexander Beregalov
[not found] ` <a4423d670905021159k51e91b12h96189005980b5e73-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-02 20:14 ` Eric Sandeen
2009-05-03 1:47 ` Ed Tomlinson
2009-05-07 23:33 ` Eric Sandeen
[not found] ` <4A036FBC.9020201-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-07 23:55 ` Eric Sandeen [this message]
[not found] ` <4A037503.1070904-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-08 1:04 ` Felix Blyakher
[not found] ` <ABCCDF18-5100-4891-AF1C-BA9513C8A334-sJ/iWh9BUns@public.gmane.org>
2009-05-08 1:09 ` Eric Sandeen
[not found] ` <4A038651.5010202-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-08 1:17 ` Felix Blyakher
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=4A037503.1070904@sandeen.net \
--to=sandeen-+82itfer+wxr7s880joybq@public.gmane.org \
--cc=a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).