xfs
[Top] [All Lists]

Re: XFS File system in trouble

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: XFS File system in trouble
From: Leslie Rhorer <lrhorer@xxxxxxxxxxxx>
Date: Mon, 20 Jul 2015 02:41:09 -0500
Cc: Kris Rusocki <kszysiu@xxxxxxxxxx>, "Rhorer, Leslie" <Leslie.Rhorer@xxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20150719232754.GS7943@dastard>
References: <03864DDC681E664EBF5D47682BE7D7CF0D3574DF@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <55AA5FCE.4080702@xxxxxxxxxxx> <03864DDC681E664EBF5D47682BE7D7CF0D358740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CAN3tLtJuk3LKHtxvbXATBR7bjr2e=GTX-fgs-jQniuxqRXjeoA@xxxxxxxxxxxxxx> <55AAF73A.4040903@xxxxxxxxxxxx> <20150719232754.GS7943@dastard>
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
On 7/19/2015 6:27 PM, Dave Chinner wrote:
On Sat, Jul 18, 2015 at 08:02:50PM -0500, Leslie Rhorer wrote:

        I found the problem with md5sum (and probably nfs, as well).  One
of the memory modules in the server was bad.  The problem with XFS
persists.  Every time tar tried to create the directory:

Now you need to run xfs_repair.

I do that every time the array implodes. It makes no difference. It never mentions cleaning the structure tar says needs cleaning, and the next time I run tar on that file, the filesystem craters.

<Prev in Thread] Current Thread [Next in Thread>