From: Leo Davis <leo1783@yahoo.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: bad primary superblock - bad magic number !!!
Date: Mon, 10 May 2010 11:11:45 -0700 (PDT) [thread overview]
Message-ID: <978493.86662.qm@web112902.mail.gq1.yahoo.com> (raw)
In-Reply-To: <4BE82955.2080009@sandeen.net>
[-- Attachment #1.1: Type: text/plain, Size: 1992 bytes --]
Many Thanks.
I agree. I destroy and re-create raid and everything would show up GOOD, only for it to break again.
So was wondering whether those traces would point to anything.... my prime suspect is hard drives, but those xfs msgs confused me.
Apologies for posting before carrying put more tests.
Thanks,
leo
________________________________
From: Eric Sandeen <sandeen@sandeen.net>
To: stress_buster <leo1783@yahoo.com>
Cc: xfs@oss.sgi.com
Sent: Mon, May 10, 2010 4:42:13 PM
Subject: Re: bad primary superblock - bad magic number !!!
stress_buster wrote:
> my hp proliant DL185 server hangs/crashes and sometimes do not boot
> correctly...
>
> [root@localhost dev]# xfs_repair -n /dev/cciss/c0d0p1
> Phase 1 - find and verify superblock...
> bad primary superblock - bad magic number !!!
>
> attempting to find secondary superblock...
> .....................................................................................Sorry,
> could not find valid secondary superblock
> Exiting now.
>
> [root@localhost dev]# xfs_repair -n /dev/cciss/c0d2
> Phase 1 - find and verify superblock...
> superblock read failed, offset 0, size 524288, ag 0, rval -1
>
> fatal error -- Input/output error
>
>
> [root@localhost dev]# xfs_db /dev/cciss/c0d0p1
> xfs_db: /dev/cciss/c0d0p1 is not a valid XFS filesystem (unexpected SB magic
> number 0x00000000)
>
> The next time, server didnt even boot up alright
>
> i've managed to capture the msgs & traces dumped to console. See below
>
>
> end_request: I/O error, dev cciss/c0d2, sector 0
> end_request: I/O error, dev cciss/c0d2, sector 0
> end_request: I/O error, dev cciss/c0d2, sector 1
> Quote:
> ciss: cmd f6c00000 has CHECK CONDITION sense key = 0x4
> end_request: I/O error, dev cciss/c0d3, sector 0
> cciss: cmd f6c00000 has CHECK CONDITION sense key = 0x4
> end_request: I/O error, dev cciss/c0d3, sector 0
You seem to have serious storage problems that are not XFS related.
You'll need to get that resolved.
-Eric
[-- Attachment #1.2: Type: text/html, Size: 2970 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-10 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 14:54 bad primary superblock - bad magic number !!! stress_buster
2010-05-10 15:42 ` Eric Sandeen
2010-05-10 18:11 ` Leo Davis [this message]
2010-05-10 20:22 ` Emmanuel Florac
2010-05-12 9:19 ` Leo Davis
2010-05-12 12:29 ` Emmanuel Florac
2010-05-12 12:45 ` Leo Davis
2010-05-13 8:38 ` Leo Davis
2010-05-13 9:41 ` Emmanuel Florac
2010-05-13 11:00 ` Leo Davis
2010-05-13 14:03 ` Emmanuel Florac
2010-05-13 17:23 ` Stan Hoeppner
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=978493.86662.qm@web112902.mail.gq1.yahoo.com \
--to=leo1783@yahoo.com \
--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