All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos E. R." <robin.listas@telefonica.net>
To: XFS mail list <xfs@oss.sgi.com>
Subject: Re: Unable to mount a XFS filesystem
Date: Mon, 9 May 2016 14:17:32 +0200	[thread overview]
Message-ID: <57307FDC.4090608@telefonica.net> (raw)
In-Reply-To: <690ueikfQ0112S06.1462789962@web06.cms.usa.net>


[-- Attachment #1.1: Type: text/plain, Size: 1817 bytes --]

On 2016-05-09 12:32, issa-gorissen@usa.net wrote:
> Received: 09:18 PM CEST, 05/08/2016
> From: "Carlos E. R." <>
> 
>>
>> How did you do that upgrade? Zypper dup, or boot dvd, choose upgrade?
>>
> In fact it was not a "real" upgrade. I added a new boot disk on which I
> installed Tumbleweed as a new OS. The MD RAID disks were kept in the computer.
> It seems the install did something to it I don't know about.

Ah, then it is a fresh install, inheriting data disks.

Then you probably keep the old boot disk. Perhaps you could try it and
find out if it still can mount the raid filesystem. If that is so,
perhaps data can be rescued. If you don't have a spare disk for a
backup, you might remove one side of the mirror and create it there,
then create again the raid in TW.

If you don't have the old boot disk, you can create a boot media on an
USB stick. You can use the 12.3 XFCE rescue image:

http://download.opensuse.org/distribution/13.2/iso/openSUSE-13.2-Rescue-CD-x86_64.iso

just cp it to the raw usb device, and boot it.


But leave that procedure as a last resource; wait for more comments or
ideas ;-)


>> Me, I would try to find out if the array is readable:
>>
>> dd if=/dev/md0 of=/dev/null
>>
> 
> array is fine but somehow the md partitions have been shrunk with the
> superblock moved. Don't know know. Version of the superblock is 1.0; which is
> stored at the end of the partition. So XFS filesystem starts at the start of
> the partition. If after the new OS install I cannot mount XFS anymore, and as
> Dave said XFS mount will try to read end of filesystem; then the end of the
> partition have changed.

Yes, I read his post. My idea was wrong, then.


-- 
Cheers / Saludos,

		Carlos E. R.
		(from 13.1 x86_64 "Bottle" at Telcontar)


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

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

  reply	other threads:[~2016-05-09 12:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 10:32 Unable to mount a XFS filesystem issa-gorissen
2016-05-09 12:17 ` Carlos E. R. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-05-09 10:26 issa-gorissen
2016-05-08 14:12 Issa Gorissen
2016-05-08 19:18 ` Carlos E. R.
2016-05-08 20:51 ` Dave Chinner

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=57307FDC.4090608@telefonica.net \
    --to=robin.listas@telefonica.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.