From: Mark Tinguely <tinguely@sgi.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: xfs@oss.sgi.com
Subject: Re: xfs errors while unlinking filenames with hash collisions
Date: Thu, 27 Mar 2014 08:34:14 -0500 [thread overview]
Message-ID: <533428D6.507@sgi.com> (raw)
In-Reply-To: <20140327132354.GU29498@order.stressinduktion.org>
On 03/27/14 08:23, Hannes Frederic Sowa wrote:
> On Thu, Mar 27, 2014 at 08:14:06AM -0500, Mark Tinguely wrote:
>> Have you tried to run a xfs_repair on the filesystem after the reboot?
>
> Yes, I did. I still use the filesystem and it works. As soon as I try to
> remove the directory again the same splash from above happens again.
Is it the latest xfsprogs' repair?
Do you have the output from the repair still?
>> Do you fill the filesystem with the test or just part way?
>
> Just part way. The problem certainly appears with 100_000 created directories.
>
> Greetings,
>
> Hannes
okay thanks.
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-03-27 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 7:41 xfs errors while unlinking filenames with hash collisions Hannes Frederic Sowa
2014-03-27 13:14 ` Mark Tinguely
2014-03-27 13:23 ` Hannes Frederic Sowa
2014-03-27 13:34 ` Mark Tinguely [this message]
2014-03-27 14:05 ` Hannes Frederic Sowa
2014-03-27 15:15 ` Mark Tinguely
2014-03-27 15:24 ` Hannes Frederic Sowa
2014-03-27 20:36 ` Mark Tinguely
2014-03-27 20:57 ` Mark Tinguely
2014-03-27 21:15 ` Hannes Frederic Sowa
2014-03-27 21:20 ` Mark Tinguely
2014-04-01 18:49 ` [PATCH xfstests] tests for file hash collisions on xfs filesystems Hannes Frederic Sowa
2014-04-01 18:56 ` Mark Tinguely
2014-04-01 23:03 ` [PATCH v2 xfstests] add tests for unlinking directories with hash collisions Hannes Frederic Sowa
2014-04-02 12:34 ` [PATCH v3 " Hannes Frederic Sowa
2014-04-02 13:07 ` Mark Tinguely
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=533428D6.507@sgi.com \
--to=tinguely@sgi.com \
--cc=hannes@stressinduktion.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.