From: Leslie Rhorer <lrhorer@mygrande.net>
To: Kris Rusocki <kszysiu@braxis.org>,
"Rhorer, Leslie" <Leslie.Rhorer@level3.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS File system in trouble
Date: Sat, 18 Jul 2015 20:02:50 -0500 [thread overview]
Message-ID: <55AAF73A.4040903@mygrande.net> (raw)
In-Reply-To: <CAN3tLtJuk3LKHtxvbXATBR7bjr2e=GTX-fgs-jQniuxqRXjeoA@mail.gmail.com>
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:
/RAID/Server-Main/Equipment/Drive Controllers/HighPoint Adapters/Rocket
2722/Driver/RR276x/Driver/Linux/openSUSE/rr276x-suse-11.2-i386/linux/suse/i386-11.1
It would begin spitting out errors, starting with "Cannot mkdir:
Structure needs cleaning". At that point, XFS had shut down. I went
into /RAID/Server-Main/Equipment/Drive Controllers/HighPoint
Adapters/Rocket
2722/Driver/RR276x/Driver/Linux/openSUSE/rr276x-suse-11.2-i386/linux/suse/
and created the i386-11.1 directory by hand, and tar no longer starts
spitting out errors at that point, but it does start up again at
RR2782/Windows/Vista-Win2008-Win7-legacy_single/x64.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-07-19 1:03 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 [this message]
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
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=55AAF73A.4040903@mygrande.net \
--to=lrhorer@mygrande.net \
--cc=Leslie.Rhorer@level3.com \
--cc=kszysiu@braxis.org \
--cc=sandeen@sandeen.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