public inbox for linux-xfs@vger.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: Sun, 8 May 2016 21:18:20 +0200	[thread overview]
Message-ID: <572F90FC.1020201@telefonica.net> (raw)
In-Reply-To: <30479c32-e298-c64b-1964-f9c9824bfe7a@usa.net>


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

On 2016-05-08 16:12, 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.

How did you do that upgrade? Zypper dup, or boot dvd, choose upgrade?



> 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

Me, I would try to find out if the array is readable:

dd if=/dev/md0 of=/dev/null

and see where it stops.

-- 
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-08 19:18 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. [this message]
2016-05-08 20:51 ` Dave Chinner
  -- strict thread matches above, loose matches on Subject: below --
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=572F90FC.1020201@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox