From: Christoph Hellwig <hch@infradead.org>
To: cmaiolino@redhat.com
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests 276: Ensure lost+found is not created with wrong link count (V2)
Date: Wed, 4 Jan 2012 13:43:44 -0500 [thread overview]
Message-ID: <20120104184344.GA8364@infradead.org> (raw)
In-Reply-To: <1323887614-21290-1-git-send-email-cmaiolino@redhat.com>
On Wed, Dec 14, 2011 at 04:33:34PM -0200, cmaiolino@redhat.com wrote:
> From: Carlos Maiolino <cmaiolino@redhat.com>
>
> xfs_repair was leaving lost+found directory with a wrong link count when a
> cleaned inode was re-used to create lost+found. This test case confirm that,
> after xfs_repair is executed, the lost+found inode is left in a consistent
> state.
This one is missing the 276.out file. In the meantime the repository
also has testst 277 and 278 - can you resend with the output file
included against the current xfstests-dev repository?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-01-04 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 18:33 [PATCH] xfstests 276: Ensure lost+found is not created with wrong link count (V2) cmaiolino
2012-01-04 18:43 ` 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=20120104184344.GA8364@infradead.org \
--to=hch@infradead.org \
--cc=cmaiolino@redhat.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