public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair couldn't verify primary superblock
Date: Thu, 21 Apr 2016 14:34:08 -0400	[thread overview]
Message-ID: <57191D20.7020402@sandeen.net> (raw)
In-Reply-To: <7ce740a1888c4bb28ce3c30fcedbe703@ul-exc-pr-mbx11.ulaval.ca>

On 4/21/16 10:42 AM, Stéphane Larose wrote:
> Hi Eric,
> 
> Nothing more interesting. From the log:
> 
> 2016-04-04T14:48:48.735738-04:00 manitou kernel: [271211.548878] XFS (dm-24): Mounting V4 Filesystem
> 2016-04-04T14:48:48.882738-04:00 manitou kernel: [271211.694242] XFS (dm-24): Ending clean mount
> 
> Then no more logs about dm-24.
> 
> Also no errors from the underlying storage (verified in SANtricity)
> which is an IS5000. The filesystem was new, the first mount was on
> 2016-04-04.
> 
> manitou:~ # blkid /dev/dm-24
> /dev/dm-24: UUID="1da22ae2-a572-4db7-b177-b90021a20863" TYPE="xfs"
> 
> Thank you for your help,

Any chance that some other host is accessing the same LUN on the SAN?

This really looks like something external corrupted the filesystem
by writing over it...

-Eric

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

  reply	other threads:[~2016-04-21 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 17:50 xfs_repair couldn't verify primary superblock Stéphane Larose
2016-04-20 20:13 ` Eric Sandeen
2016-04-21 14:42   ` Stéphane Larose
2016-04-21 18:34     ` Eric Sandeen [this message]
2016-04-22 13:53       ` Stéphane Larose

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=57191D20.7020402@sandeen.net \
    --to=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