public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Christoph Hellwig <hch@infradead.org>,
	xfs-masters <xfs-masters@oss.sgi.com>,
	xfs@oss.sgi.com
Subject: Re: XFS inconsistent lock state (-rc4)
Date: Fri, 31 Jul 2009 07:36:52 -0400	[thread overview]
Message-ID: <20090731113652.GA31758@infradead.org> (raw)
In-Reply-To: <1249039546.29587.72.camel@johannes.local>

On Fri, Jul 31, 2009 at 01:25:46PM +0200, Johannes Berg wrote:
> After pushing a lot of data onto the disk, including creating millions
> of hardlinks (rsync backup run with --link-dest):

I've posted a fix for this to the list a while ago, still hoping that
Felix will push it for 2.6.31.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2009-07-31 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31 11:25 XFS inconsistent lock state (-rc4) Johannes Berg
2009-07-31 11:36 ` Christoph Hellwig [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=20090731113652.GA31758@infradead.org \
    --to=hch@infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=xfs-masters@oss.sgi.com \
    --cc=xfs@oss.sgi.com \
    /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