public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Leslie Rhorer <lrhorer@mygrande.net>, Dave Chinner <david@fromorbit.com>
Cc: Kris Rusocki <kszysiu@braxis.org>,
	"Rhorer, Leslie" <Leslie.Rhorer@level3.com>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS File system in trouble
Date: Fri, 24 Jul 2015 09:44:02 -0500	[thread overview]
Message-ID: <55B24F32.4080505@sandeen.net> (raw)
In-Reply-To: <55B241FC.8020207@mygrande.net>

On 7/24/15 8:47 AM, Leslie Rhorer wrote:
> On 7/22/2015 10:18 PM, Eric Sandeen wrote:
>> On 7/20/15 2:41 AM, Leslie Rhorer wrote:
>>> 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.
>>>
>>
>> What.
>> Did.
>> xfs_repair.
>> Say.
> 
> Look.
> At.
> My.
> First.
> E-mail.

Your first email contains only a narrative about repair:

"Xfs_repair completes, usually with no errors found, or sometimes one or two errors."

But we don't know what those one or two errors are.

Your second email shows the output of one instance of a completely clean repair.

Then you found out that you had bad memory, and Dave asked you to run repair again,
having fixed that hardware issue.

You said it "never mentions cleaning the structure tar says needs cleaning"

What I am asking you is for the full repair output now, so we can see what it
*did* say, rather than an interpreted narrative about what it did not say.

Stating "repair found no errors" would also be helpful.  Your reply above implies
that maybe it did find errors, but not ones you felt were related.  I'd simply like
to know the details, so we can continue to try to resolve your problem.

-Eric

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

  reply	other threads:[~2015-07-24 14:44 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-18  1:46 XFS File system in trouble Rhorer, Leslie
2015-07-18 14:16 ` Eric Sandeen
2015-07-18 17:23   ` Rhorer, Leslie
2015-07-18 17:47     ` Kris Rusocki
2015-07-18 18:12       ` Leslie Rhorer
2015-07-19  1:02       ` Leslie Rhorer
2015-07-19 23:27         ` Dave Chinner
2015-07-20  7:41           ` Leslie Rhorer
2015-07-20  8:05             ` Martin Papik
2015-07-20  8:35               ` Leslie Rhorer
2015-07-20  8:52                 ` Martin Papik
2015-07-20 13:08                 ` Gim Leong Chin
2015-07-20 13:34             ` Eric Sandeen
2015-07-23  3:18             ` Eric Sandeen
2015-07-24 13:47               ` Leslie Rhorer
2015-07-24 14:44                 ` Eric Sandeen [this message]
2015-07-24 15:29                   ` Rhorer, Leslie
2015-07-20 11:17         ` Brian Foster
2015-07-23  1:45           ` Leslie Rhorer
2015-07-23 11:36             ` Brian Foster
2015-07-28  7:46           ` Leslie Rhorer
2015-07-28  8:35             ` Stefan Ring
2015-07-28 10:48             ` Roger Willcocks
2015-07-28 12:33             ` Brian Foster
2015-07-28 15:13               ` Leslie Rhorer
2015-07-28 16:53                 ` Eric Sandeen
2015-07-28 19:12                   ` Martin Papik
2015-07-28 19:52                     ` Martin Steigerwald
2015-07-28 22:11                 ` Brian Foster
2015-08-02 20:24                   ` Leslie Rhorer
2015-08-04  7:52                     ` Leslie Rhorer
2015-08-04 12:19                       ` Brian Foster
2015-08-04 22:42                       ` Dave Chinner
2015-08-10  1:37                         ` Leslie Rhorer
2015-08-13  6:21                           ` Leslie Rhorer
2015-08-14  1:26                             ` Dave Chinner
2015-08-14 23:12                               ` Leslie Rhorer
2015-08-15 12:28                                 ` Roger Willcocks
2015-08-15 18:48                                   ` Eric Sandeen
2015-08-15 18:57                                     ` Roger Willcocks
2015-08-15 22:48                                       ` Dave Chinner
2015-08-15 19:00                                     ` Eric Sandeen
2015-08-15 19:13                                       ` Roger Willcocks
2015-08-16  0:32                                       ` Eric Sandeen
2015-08-18  2:14                                 ` Dave Chinner

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=55B24F32.4080505@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=Leslie.Rhorer@level3.com \
    --cc=david@fromorbit.com \
    --cc=kszysiu@braxis.org \
    --cc=lrhorer@mygrande.net \
    --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