xfs
[Top] [All Lists]

Re: Cant mount xfs lvm. Experimental Features?

To: weber@xxxxxxxxxx, Xfs <xfs@xxxxxxxxxxx>
Subject: Re: Cant mount xfs lvm. Experimental Features?
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 25 Aug 2015 15:04:37 -0500
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <accadc1d9218bdf0935af4bb1f1446f7@xxxxxxxxxx>
References: <8a6d5afa8829aec73d911f35815d7b92@xxxxxxxxxx> <20150825115412.GI714@dastard> <5ab00519660fd5ed1b3d347658dba1f2@xxxxxxxxxx> <55DCB158.20505@xxxxxxxxxxx> <accadc1d9218bdf0935af4bb1f1446f7@xxxxxxxxxx>
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

<Prev in Thread] Current Thread [Next in Thread>