From: MikeJeezy <forums@mgaccess.net>
To: xfs@oss.sgi.com
Subject: Re: mount: Structure needs cleaning
Date: Sat, 25 Feb 2012 23:22:29 -0800 (PST) [thread overview]
Message-ID: <33393429.post@talk.nabble.com> (raw)
In-Reply-To: <4F49B693.4080309@hardwarefreak.com>
On 02/25/2012 10:35pm, Stan Hoeppner wrote:
>Can you run xfs_check on the filesystem to determine if a freespace
>tree is corrupted (post the output if it is), then run xfs_repair
>to rebuild them?"
Thank you for responding. This is a 24/7 production server and I did not
anticipate getting a response this late on a Saturday, so I panicked quite
frankly, and went ahead and ran "xfs_repair -L" on both volumes. I can now
mount the volumes and everything looks okay as far as I can tell. There
were only 2 files in the "lost+found" directory after the repair. Does that
mean only two files were lost? Is there any way to tell how many files were
lost?
>This corruption could have happened a long time ago in the past, and
>it may simply be coincidental that you've tripped over this at
>roughly the same time you upgraded the kernel.
It would be nice to find out why this happened. I suspect it is as you
suggested, previous corruption and not a hardware issue, because I have
other volumes mounted to other VM's that are attached to the same SAN
controller / RAID6 Array... and they did not have any issues - only this one
VM.
>So, run "xfs_check /dev/sde1" and post the output here. Then await
>further instructions.
Can I still do this (or anything) to help uncover any causes or is it too
late? I have also run yum update on the server because it was out of date.
--
View this message in context: http://old.nabble.com/mount%3A-Structure-needs-cleaning-tp33393100p33393429.html
Sent from the Xfs - General mailing list archive at Nabble.com.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-26 7:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 3:15 mount: Structure needs cleaning MikeJeezy
2012-02-26 4:35 ` Stan Hoeppner
2012-02-26 7:22 ` MikeJeezy [this message]
2012-02-26 17:07 ` Stan Hoeppner
2012-02-27 0:49 ` Dave Chinner
2012-02-27 3:11 ` MikeJeezy
2012-02-27 6:28 ` Stan Hoeppner
2012-02-27 18:32 ` MikeJeezy
2012-02-28 1:48 ` Dave Chinner
2012-02-28 9:14 ` Brian Candler
2012-02-29 3:50 ` Dave Chinner
2012-02-29 7:40 ` Brian Candler
-- strict thread matches above, loose matches on Subject: below --
2014-10-12 8:43 Mount: " tommason
2014-10-12 14:20 ` Brian Foster
2014-10-12 22:39 ` tom mason
2014-10-12 22:48 ` tom mason
2014-10-12 22:51 ` tom mason
2014-10-12 23:10 ` Dave Chinner
2014-10-13 10:05 ` Tom Mason
2014-10-13 10:19 ` Emmanuel Florac
2014-10-13 10:40 ` Tom Mason
2014-10-13 9:26 ` Emmanuel Florac
2014-10-13 20:33 Tom Mason
2014-10-13 22:09 ` Dave Chinner
2014-10-13 22:25 ` Tom Mason
2014-10-13 23:44 ` Dave Chinner
2014-10-13 22:38 ` Tom Mason
2014-10-13 23:47 ` Dave Chinner
2014-10-14 10:55 ` Emmanuel Florac
2014-10-14 15:46 ` Tom Mason
2014-10-14 16:38 ` Emmanuel Florac
2014-10-14 16:43 ` Tom Mason
2014-10-21 20:44 ` Tom Mason
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=33393429.post@talk.nabble.com \
--to=forums@mgaccess.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 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.