public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Robert Tench <robtench@hotmail.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Mismatch UUID
Date: Fri, 14 Nov 2014 08:42:08 -0500	[thread overview]
Message-ID: <20141114134208.GB36731@bfoster.bfoster> (raw)
In-Reply-To: <BLU172-W9B4FE524F07D7E6D5592BC48C0@phx.gbl>

On Fri, Nov 14, 2014 at 07:57:42PM +1100, Robert Tench wrote:
>                                                             Robert has a file to share with you on OneDrive. To view it, click the link below.                                                                                                        xfs.log                                                                            So finally have managed to find a way to save the complete log of running xfs_repair -n /dev.md4
> 
> And below is the output of xfs_check /dev/md4
> 
> root@ubuntu:~# xfs_check /dev/md4
> * ERROR: mismatched uuid in log
> *            SB : 813833a7-1bd3-4447-b575-09d1471bb652
> *            log: ea3833af-25ce-9f91-b575-018fb49df3b1
> ERROR: The filesystem has valuable metadata changes in a log which needs to
> be replayed.  Mount the filesystem to replay the log, and unmount it before
> re-running xfs_check.  If you are unable to mount the filesystem, then use
> the xfs_repair -L option to destroy the log and attempt a repair.
> Note that destroying the log may cause corruption -- please attempt a mount
> of the filesystem before doing this.
> 

You want to use xfs_repair (-n) rather than xfs_check. I think you
mentioned in your other email you've tried xfs_repair..? The above
message indicates a dirty log, have you attempted to mount the device to
replay the log?

> And the output from mdadm -D /dev/md4 is as follows
> 

How did you put the array back together? Did it assemble fine or did you
have to recreate it? If the latter, how are you sure the geometry is
correct (it looks like it's syncing)?

Brian

> root@ubuntu:~# mdadm -D /dev/md4
> /dev/md4:
>         Version : 1.0
>   Creation Time : Fri Jan  1 01:31:17 2010
>      Raid Level : raid5
>      Array Size : 11712962560 (11170.35 GiB 11994.07 GB)
>   Used Dev Size : 2928240640 (2792.59 GiB 2998.52 GB)
>    Raid Devices : 5
>   Total Devices : 5
>     Persistence : Superblock is persistent
> 
>     Update Time : Fri Nov 14 15:58:16 2014
>           State : clean 
>  Active Devices : 5
> Working Devices : 5
>  Failed Devices : 0
>   Spare Devices : 0
> 
>          Layout : left-symmetric
>      Chunk Size : 512K
> 
>            Name : (none):4
>            UUID : e0829810:9782b51f:25529f65:8823419c
>          Events : 1243386
> 
>     Number   Major   Minor   RaidDevice State
>        0       8        2        0      active sync   /dev/sda2
>        6       8       18        1      active sync   /dev/sdb2
>        2       8       34        2      active sync   /dev/sdc2
>        5       8       50        3      active sync   /dev/sdd2
>        4       8       66        4      active sync   /dev/sde2
> 
> 
> And then the response from mdadm -E /dev/md4
> 
> root@ubuntu:~# mdadm -E /dev/md4
> mdadm: No md superblock detected on /dev/md4.
> 
> Not sure what to do, any help would be appreciated
> 
> Regards,
> 
> Rob
> 
> 
> 
>                  		 	   		  

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

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

  reply	other threads:[~2014-11-14 13:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14  8:57 Mismatch UUID Robert Tench
2014-11-14 13:42 ` Brian Foster [this message]
     [not found]   ` <BLU172-W1423188AD065CADCC115E6C48C0@phx.gbl>
2014-11-15 14:27     ` Brian Foster
2014-11-14 22:31 ` Chris Murphy
2014-11-14 23:40   ` Eric Sandeen
2014-11-15  0:03     ` Chris Murphy
2014-11-15  2:17     ` Robert Tench
2014-11-15 14:39       ` Brian Foster
2014-11-15  2:58     ` Robert Tench

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=20141114134208.GB36731@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=robtench@hotmail.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