All of lore.kernel.org
 help / color / mirror / Atom feed
From: issa-gorissen@usa.net
To: xfs@oss.sgi.com
Subject: Re: Unable to mount a XFS filesystem
Date: Mon, 09 May 2016 12:26:37 +0200	[thread overview]
Message-ID: <057ueikZl3984S04.1462789597@web04.cms.usa.net> (raw)

------ Original Message ------
Received: 10:51 PM CEST, 05/08/2016
From: Dave Chinner <david@fromorbit.com>

> Yup, the kernel also emits the same error on the same check - most
> likely during your upgrade the MD RAID device has changed size and
> is now 112 sectors smaller than before, hence the filesystem will
> refuse to mount.
> 

> 
> Unlikely to be an XFS problem, more likely a MD device/upgrade issue.


Thanks Dave for your pointer.

As I don't have much experiences in debugging XFS or MD RAID; I just took a
shortcut.

Your input helped a little.

I tried to resize the MD partition (for the missing sectors XFS was
complaining about) but as the MD superblock is at the end on my partition,
after the resize, mdadm could not find back the superblock and I did not want
to spend time trying to move the superblock along with the partition resize
(don't know if this is feasable).

So of one of the two disks; I could mount the resized MD partition as a XFS
filesystem after a xfs_repair on it. The folders structure is lost as
everything is in random folders in lost+found; but it seems the files are
there.

So I will create a new MD RAID from the disk I could mount.

It seems the setup of openSuse Tumbleweed messed up with my md raid
partitions! :-(

Thx,
--
Issa

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

             reply	other threads:[~2016-05-09 10:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 10:26 issa-gorissen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-05-09 10:32 Unable to mount a XFS filesystem issa-gorissen
2016-05-09 12:17 ` Carlos E. R.
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=057ueikZl3984S04.1462789597@web04.cms.usa.net \
    --to=issa-gorissen@usa.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.