From: Eric Sandeen <sandeen@sandeen.net>
To: weber@zbfmail.de, Xfs <xfs@oss.sgi.com>
Subject: Re: Cant mount xfs lvm. Experimental Features?
Date: Tue, 25 Aug 2015 15:04:37 -0500 [thread overview]
Message-ID: <55DCCA55.4010901@sandeen.net> (raw)
In-Reply-To: <accadc1d9218bdf0935af4bb1f1446f7@zbfmail.de>
On 8/25/15 2:26 PM, Marko Weber|8000 wrote:
>>> pvdisplay shows:
>>>
>>> # pvdisplay
>>> --- Physical volume ---
>>> PV Name /dev/md4
>>> VG Name VolGroup01
>>> PV Size 2.69 TiB / not usable 1.25 MiB
>>>
>>>
>>> so what is XFS missing?
>>
>> what does blkid /dev/md4 say?
>>
>> It looks like you might have a storage problem, now, and xfs can't
>> even find a proper magic number on that device.
>
> smartcl says all is ok.
> AND the othetr two lvm partitions get mounted well....
>
> blkid output:
>
> ~ # blkid /dev/md4
> /dev/md4: UUID="7LYlkp-33ro-qyal-yGkZ-pMwC-Ei1L-Viy4UJ" TYPE="LVM2_member"
Sorry, I shouldn't have asked for /dev/md4; that's your physical volume,
not a logical volume. I meant to ask for blkid of whatever dm-2 is.
Anyway, from:
> Aug 25 18:44:01 backupserver kernel: XFS (dm-2): Invalid superblock magic number
it seems that the dm-2 device doesn't actually contain an xfs filesystem,
so this looks like a storage config problem, not an xfs problem.
-Eric
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-08-25 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 8:25 Cant mount xfs lvm. Experimental Features? Marko Weber|8000
2015-08-25 11:54 ` Dave Chinner
2015-08-25 16:51 ` Marko Weber|8000
2015-08-25 18:18 ` Eric Sandeen
2015-08-25 19:26 ` Marko Weber|8000
2015-08-25 20:04 ` Eric Sandeen [this message]
2015-08-25 22:53 ` Marko Weber|8000
2015-08-25 22:58 ` Eric Sandeen
2015-08-25 23:02 ` Marko Weber|8000
2015-08-25 23:16 ` Dave Chinner
2015-08-25 23:03 ` Dave Chinner
2015-08-25 23:10 ` Marko Weber|8000
2015-08-25 23:33 ` Dave Chinner
2015-08-26 10:30 ` Marko Weber|8000
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=55DCCA55.4010901@sandeen.net \
--to=sandeen@sandeen.net \
--cc=weber@zbfmail.de \
--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.