All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Issa Gorissen <issa-gorissen@usa.net>
Cc: xfs@oss.sgi.com
Subject: Re: Unable to mount a XFS filesystem
Date: Mon, 9 May 2016 06:51:34 +1000	[thread overview]
Message-ID: <20160508205134.GH26977@dastard> (raw)
In-Reply-To: <30479c32-e298-c64b-1964-f9c9824bfe7a@usa.net>

On Sun, May 08, 2016 at 04:12:59PM +0200, Issa Gorissen wrote:
> Hello,
> 
> After I have upgraded my htpc from openSuse 12.3 running kernel
> 3.7.10 to openSuse Tumbleweed running kernel 4.5.2; I am unable to
> mount my XFS filesystem anymore.
....
>  Avail Dev Size : 5860529896 (2794.52 GiB 3000.59 GB)
>      Array Size : 2930264896 (2794.52 GiB 3000.59 GB)
>   Used Dev Size : 5860529792 (2794.52 GiB 3000.59 GB)
>    Super Offset : 5860530160 sectors
>    Unused Space : before=0 sectors, after=344 sectors

Both devices are reporting 344 unused sectors. Which may be
important, because....

.....
> tv:/ # xfs_db /dev/md0
> xfs_db: error - read only 0 of 512 bytes

... something is wrong with the RAID device for this error to be
emitted. XFS checks to see if it can access the last sector of the
filesystem before it starts using it, and this is indicative of a
that read being beyond the end of the device.

> tv:/ # mount -t xfs /dev/md0 /data
> mount: /dev/md0: can't read superblock
> 
> dmesg outputs
> 
> 
> [ 5525.861750] SGI XFS with ACLs, security attributes, realtime, no
> debug enabled
> [ 5525.862231] attempt to access beyond end of device
> [ 5525.862232] md0: rw=32, want=5860529904, limit=5860529792
> [ 5525.862234] XFS (md0): last sector read failed

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.

> Any pointers to fix this ? It seems the disks still contains a XFS
> filesystem but for some reason, I cannot access it.

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

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  parent reply	other threads:[~2016-05-08 20:51 UTC|newest]

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

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=20160508205134.GH26977@dastard \
    --to=david@fromorbit.com \
    --cc=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.