From: Stefanita Rares Dumitrescu <katmai@keptprivate.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs corrupted
Date: Tue, 15 Oct 2013 20:45:59 +0200 [thread overview]
Message-ID: <525D8D67.2090301@keptprivate.com> (raw)
In-Reply-To: <20131015203434.2f336fd8@galadriel.home>
That was the first thing i checked: the array was optimal, and i checked
each drive with smartctl, and they are all fine.
I left the xfs_repair on for the night, and it showed no progress. I was
actually thinking that maybe the memory is bad, so i took the server
offline this morning, and ran a memtest for 3 hours, which showed
nothing wrong with the sticks, however good news:
I was able to mount the array, but i can only read from it. Whenever i
try to write something, it just hangs right there.
I ran an xfs_repair -n on the second array, which is 18 tb in size as
opposed to the 14 tb first one, and that check completed in like 10
minutes.
I am running now xfs_repair -n on the 14 tb bad array, and it's stuck
here for about 5 hours now.
[root@kp4 ~]# umount /home
[root@kp4 ~]# xfs_repair -n /dev/sdc
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
What worries me is that i see 100 % cpu usage, some 74 % memory usage (i
have 4 gb ram) but there is no disk activity at all. I was thinking that
it would be at least some reads if the xfs_repair is doing something.
On 15/10/2013 20:34, Emmanuel Florac wrote:
> Le Tue, 15 Oct 2013 01:41:47 -0700 (PDT) vous écriviez:
>
>> Did i jump the gun by using the -L switch :/ ?
>
> You should have checked that the RAID is optimal first! In case of a
> flailing hardware, any write to the volume can exacerbate problems.
>
> You should use arcconf to check for the RAID state (arcconf getstatus
> 1) and eventually run a RAID repair (arcconf task start 1 logicaldrive
> 0 verify_fix).
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-10-15 18:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 8:41 xfs corrupted katmai
2013-10-15 18:34 ` Emmanuel Florac
2013-10-15 18:45 ` Stefanita Rares Dumitrescu [this message]
2013-10-15 19:07 ` Chris Murphy
2013-10-15 19:52 ` Emmanuel Florac
2013-10-15 19:34 ` Emmanuel Florac
2013-10-15 19:57 ` Stefanita Rares Dumitrescu
2013-10-15 20:05 ` Emmanuel Florac
2013-10-15 20:17 ` Stefanita Rares Dumitrescu
2013-10-15 20:18 ` Stefanita Rares Dumitrescu
2013-10-15 20:26 ` Dave Chinner
2013-10-16 12:23 ` Stefanita Rares Dumitrescu
2013-10-16 13:32 ` Stefanita Rares Dumitrescu
2013-10-16 17:33 ` Keith Keller
2013-10-16 22:16 ` Dave Chinner
2013-10-16 14:32 ` Stefanita Rares Dumitrescu
2013-10-16 20:52 ` Stefanita Rares Dumitrescu
2013-10-17 18:04 ` Stefanita Rares Dumitrescu
2013-10-15 20:02 ` Stefanita Rares Dumitrescu
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=525D8D67.2090301@keptprivate.com \
--to=katmai@keptprivate.com \
--cc=eflorac@intellique.com \
--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