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: Chris Murphy <lists@colorremedies.com>,
	Eric Sandeen <sandeen@sandeen.net>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Mismatch UUID
Date: Sat, 15 Nov 2014 09:39:51 -0500	[thread overview]
Message-ID: <20141115143951.GB54930@bfoster.bfoster> (raw)
In-Reply-To: <BLU172-W19A7DE957502A2F854163FC48D0@phx.gbl>

On Sat, Nov 15, 2014 at 01:17:39PM +1100, Robert Tench wrote:
> Hi all,
> 
> Many thanks for the replies so far.
> 
> So here is the reponse from the command line mdadm -E /dev/sd[abcde]2
> 
> ubuntu@ubuntu:~$ sudo mdadm -E /dev/sd[abcde]2
> /dev/sda2:
>           Magic : a92b4efc
>         Version : 1.0
>     Feature Map : 0x0
>      Array UUID : e0829810:9782b51f:25529f65:8823419c
>            Name : (none):4
>   Creation Time : Fri Jan  1 01:31:17 2010
>      Raid Level : raid5
>    Raid Devices : 5
> 
>  Avail Dev Size : 5856481280 (2792.59 GiB 2998.52 GB)
>      Array Size : 11712962560 (11170.35 GiB 11994.07 GB)
>    Super Offset : 5856481536 sectors
>           State : clean
>     Device UUID : d405d0c5:2a07d7ed:27abcb5a:0eeadc7d
> 
>     Update Time : Fri Nov 14 15:58:16 2014
>        Checksum : c082e9bb - correct
>          Events : 1243386
> 
>          Layout : left-symmetric
>      Chunk Size : 512K
> 
>    Device Role : Active device 0
>    Array State : AAAAA ('A' == active, '.' == missing)
> /dev/sdb2:
>           Magic : a92b4efc
>         Version : 1.0
>     Feature Map : 0x0
>      Array UUID : e0829810:9782b51f:25529f65:8823419c
>            Name : (none):4
>   Creation Time : Fri Jan  1 01:31:17 2010
>      Raid Level : raid5
>    Raid Devices : 5
> 
>  Avail Dev Size : 5856481280 (2792.59 GiB 2998.52 GB)
>      Array Size : 11712962560 (11170.35 GiB 11994.07 GB)
>    Super Offset : 5856481536 sectors
>           State : clean
>     Device UUID : 33acf23a:52a0ad00:cda69d9f:468a8c13
> 
>     Update Time : Fri Nov 14 15:58:16 2014
>        Checksum : 22fdc525 - correct
>          Events : 1243386
> 
>          Layout : left-symmetric
>      Chunk Size : 512K
> 
>    Device Role : Active device 1
>    Array State : AAAAA ('A' == active, '.' == missing)
> /dev/sdc2:
>           Magic : a92b4efc
>         Version : 1.0
>     Feature Map : 0x0
>      Array UUID : e0829810:9782b51f:25529f65:8823419c
>            Name : (none):4
>   Creation Time : Fri Jan  1 01:31:17 2010
>      Raid Level : raid5
>    Raid Devices : 5
> 
>  Avail Dev Size : 5856481280 (2792.59 GiB 2998.52 GB)
>      Array Size : 11712962560 (11170.35 GiB 11994.07 GB)
>    Super Offset : 5856481536 sectors
>           State : clean
>     Device UUID : 1a4f20e2:34926568:af5351a1:9c9f60e9
> 
>     Update Time : Fri Nov 14 15:58:16 2014
>        Checksum : 96b21ac - correct
>          Events : 1243386
> 
>          Layout : left-symmetric
>      Chunk Size : 512K
> 
>    Device Role : Active device 2
>    Array State : AAAAA ('A' == active, '.' == missing)
> /dev/sdd2:
>           Magic : a92b4efc
>         Version : 1.0
>     Feature Map : 0x0
>      Array UUID : e0829810:9782b51f:25529f65:8823419c
>            Name : (none):4
>   Creation Time : Fri Jan  1 01:31:17 2010
>      Raid Level : raid5
>    Raid Devices : 5
> 
>  Avail Dev Size : 5856481280 (2792.59 GiB 2998.52 GB)
>      Array Size : 11712962560 (11170.35 GiB 11994.07 GB)
>    Super Offset : 5856481536 sectors
>           State : clean
>     Device UUID : 0ee6b711:242fbd18:44c2839e:60e8ad0d
> 
>     Update Time : Fri Nov 14 15:58:16 2014
>        Checksum : ada0762 - correct
>          Events : 1243386
> 
>          Layout : left-symmetric
>      Chunk Size : 512K
> 
>    Device Role : Active device 3
>    Array State : AAAAA ('A' == active, '.' == missing)
> /dev/sde2:
>           Magic : a92b4efc
>         Version : 1.0
>     Feature Map : 0x0
>      Array UUID : e0829810:9782b51f:25529f65:8823419c
>            Name : (none):4
>   Creation Time : Fri Jan  1 01:31:17 2010
>      Raid Level : raid5
>    Raid Devices : 5
> 
>  Avail Dev Size : 5856481280 (2792.59 GiB 2998.52 GB)
>      Array Size : 11712962560 (11170.35 GiB 11994.07 GB)
>    Super Offset : 5856481536 sectors
>           State : clean
>     Device UUID : f89fdd4c:627a6650:3de0dcab:6790076f
> 
>     Update Time : Fri Nov 14 15:58:16 2014
>        Checksum : ec5bd289 - correct
>          Events : 1243386
> 
>          Layout : left-symmetric
>      Chunk Size : 512K
> 
>    Device Role : Active device 4
>    Array State : AAAAA ('A' == active, '.' == missing)
> 
> 
> What I am curious about is how I should go about attempting to Mount the device and the command line needed. Am I mounting the Raid Array /dev/md4, or am I trying to mount the XFS data partitions contained within with would be made up of /dev/sd[abcde2]? I am a little bit confused by all the various options and what I am exactly suppose to use given being a complete linux novice.
> 

Normally the array (/dev/md*) is used directly, but I suppose it could
be partitioned. It depends on how the storage is configured. It does
look like you have several arrays configured from the log snippet in the
subsequent mail.

What does 'cat /proc/mdstat' on the box show? How about 'file -s
/dev/md##' for each md device specified in the former output?

Brian

> Any help is appreciated?
> 
> Rob
> 
> 
> > Date: Fri, 14 Nov 2014 17:40:10 -0600
> > From: sandeen@sandeen.net
> > To: lists@colorremedies.com; robtench@hotmail.com
> > CC: xfs@oss.sgi.com
> > Subject: Re: Mismatch UUID
> > 
> > On 11/14/14 4:31 PM, Chris Murphy wrote:
> > 
> > > It’s very good to ask instead of haphazardly trying things. Trying to
> > > normally mount the file system should be safe; and then use dmesg to
> > > check for kernel messages. The xfs kernel code is responsible for log
> > > replay and making most kinds of repairs, anything it can’t deal with
> > > will be reported as a kernel message. If mount fails, report kernel
> > > xfs related messages, and also the results from xfs_check -n.
> > 
> > xfs_repair -n
> > 
> > xfs_check is deprecated and has no -n option ;)
> > 
> > -Eric
>  		 	   		  

> _______________________________________________
> 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-15 14:40 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
     [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 [this message]
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=20141115143951.GB54930@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=lists@colorremedies.com \
    --cc=robtench@hotmail.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