Cant mount xfs lvm. Experimental Features?

Cant mount xfs lvm. Experimental Features?

[Marko Weber|8000]

Hello List, Hello Dave...


i try to mount on my backup server an Lvm Partition and get errors in 
stdout and log:




stdout:

mount: wrong fs type, bad option, bad superblock on 
/dev/mapper/VolGroup01-storage01,
        missing codepage or helper program, or other error

        In some cases useful info is found in syslog - try
        dmesg | tail or so.



/var/log/messages:

Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Version 5 superblock 
detected. This kernel has EXPERIMENTAL support enabled!
Aug 25 10:20:31 backupserver kernel: Use of these features in this 
kernel is at your own risk!
Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Superblock has unknown 
read-only compatible features (0x1) enabled.
Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Attempted to mount 
read-only compatible filesystem read-write.
Aug 25 10:20:31 backupserver kernel: Filesystem can only be safely 
mounted read only.
Aug 25 10:20:31 backupserver kernel: XFS (dm-2): SB validate failed with 
error 22.



How do i solve this?
I dont remember to have activated any experimental features in kernel.


thanks,

marko




-- 
zbfmail - Mittendrin statt nur Datei!

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

Re: Cant mount xfs lvm. Experimental Features?

[Dave Chinner]

On Tue, Aug 25, 2015 at 10:25:16AM +0200, Marko Weber|8000 wrote:
> 
> Hello List, Hello Dave...
> 
> 
> i try to mount on my backup server an Lvm Partition and get errors
> in stdout and log:
> 
> /var/log/messages:
> 
> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Version 5
> superblock detected. This kernel has EXPERIMENTAL support enabled!
> Aug 25 10:20:31 backupserver kernel: Use of these features in this
> kernel is at your own risk!
> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Superblock has
> unknown read-only compatible features (0x1) enabled.
> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Attempted to mount
> read-only compatible filesystem read-write.
> Aug 25 10:20:31 backupserver kernel: Filesystem can only be safely
> mounted read only.
> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): SB validate failed
> with error 22.

You need to run the same version kernel on both servers. The primary
has a more recent kernel and feature set than your older backup
server is running.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

Re: Cant mount xfs lvm. Experimental Features?

[Marko Weber|8000]

dave,

Am 2015-08-25 13:54, schrieb Dave Chinner:
> On Tue, Aug 25, 2015 at 10:25:16AM +0200, Marko Weber|8000 wrote:
>> 
>> Hello List, Hello Dave...
>> 
>> 
>> i try to mount on my backup server an Lvm Partition and get errors
>> in stdout and log:
>> 
>> /var/log/messages:
>> 
>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Version 5
>> superblock detected. This kernel has EXPERIMENTAL support enabled!
>> Aug 25 10:20:31 backupserver kernel: Use of these features in this
>> kernel is at your own risk!
>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Superblock has
>> unknown read-only compatible features (0x1) enabled.
>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Attempted to mount
>> read-only compatible filesystem read-write.
>> Aug 25 10:20:31 backupserver kernel: Filesystem can only be safely
>> mounted read only.
>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): SB validate failed
>> with error 22.
> 
> You need to run the same version kernel on both servers. The primary
> has a more recent kernel and feature set than your older backup
> server is running.
> 
> Cheers,
> 
> Dave.

you was right.
There was new kernel built. /usr/src/linux pointed to new kernel source.
But machine was not rebooted. So kernel version before kernel built was 
loaded.
I rebooted machine.
i renoved logical volume
i created logical volume
i tried to mount it and get:

Aug 25 18:43:15 backupserver kernel: md4: unknown partition table
Aug 25 18:43:15 backupserver syslog-ng[1417]: Internal error, 
alarm_set() called while an alarm is still active;
Aug 25 18:43:56 backupserver kernel: md4: unknown partition table
Aug 25 18:44:01 backupserver kernel: XFS (dm-2): Invalid superblock 
magic number

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?

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

Re: Cant mount xfs lvm. Experimental Features?

[Eric Sandeen]

On 8/25/15 11:51 AM, Marko Weber|8000 wrote:
> 
> dave,
> 
> Am 2015-08-25 13:54, schrieb Dave Chinner:
>> On Tue, Aug 25, 2015 at 10:25:16AM +0200, Marko Weber|8000 wrote:
>>>
>>> Hello List, Hello Dave...
>>>
>>>
>>> i try to mount on my backup server an Lvm Partition and get errors
>>> in stdout and log:
>>>
>>> /var/log/messages:
>>>
>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Version 5
>>> superblock detected. This kernel has EXPERIMENTAL support enabled!
>>> Aug 25 10:20:31 backupserver kernel: Use of these features in this
>>> kernel is at your own risk!
>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Superblock has
>>> unknown read-only compatible features (0x1) enabled.
>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Attempted to mount
>>> read-only compatible filesystem read-write.
>>> Aug 25 10:20:31 backupserver kernel: Filesystem can only be safely
>>> mounted read only.
>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): SB validate failed
>>> with error 22.
>>
>> You need to run the same version kernel on both servers. The primary
>> has a more recent kernel and feature set than your older backup
>> server is running.
>>
>> Cheers,
>>
>> Dave.
> 
> you was right.
> There was new kernel built. /usr/src/linux pointed to new kernel source.
> But machine was not rebooted. So kernel version before kernel built was loaded.
> I rebooted machine.
> i renoved logical volume
> i created logical volume

Hope it landed back in the same place!

> i tried to mount it and get:
> 
> Aug 25 18:43:15 backupserver kernel: md4: unknown partition table
> Aug 25 18:43:15 backupserver syslog-ng[1417]: Internal error, alarm_set() called while an alarm is still active;
> Aug 25 18:43:56 backupserver kernel: md4: unknown partition table
> Aug 25 18:44:01 backupserver kernel: XFS (dm-2): Invalid superblock magic number
> 
> 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.

-Eric


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

Re: Cant mount xfs lvm. Experimental Features?

[Marko Weber|8000]

hi eric,


> Am 2015-08-25 20:18, schrieb Eric Sandeen:
> On 8/25/15 11:51 AM, Marko Weber|8000 wrote:
>> 
>> dave,
>> 
>> Am 2015-08-25 13:54, schrieb Dave Chinner:
>>> On Tue, Aug 25, 2015 at 10:25:16AM +0200, Marko Weber|8000 wrote:
>>>> 
>>>> Hello List, Hello Dave...
>>>> 
>>>> 
>>>> i try to mount on my backup server an Lvm Partition and get errors
>>>> in stdout and log:
>>>> 
>>>> /var/log/messages:
>>>> 
>>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Version 5
>>>> superblock detected. This kernel has EXPERIMENTAL support enabled!
>>>> Aug 25 10:20:31 backupserver kernel: Use of these features in this
>>>> kernel is at your own risk!
>>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Superblock has
>>>> unknown read-only compatible features (0x1) enabled.
>>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Attempted to mount
>>>> read-only compatible filesystem read-write.
>>>> Aug 25 10:20:31 backupserver kernel: Filesystem can only be safely
>>>> mounted read only.
>>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): SB validate failed
>>>> with error 22.
>>> 
>>> You need to run the same version kernel on both servers. The primary
>>> has a more recent kernel and feature set than your older backup
>>> server is running.
>>> 
>>> Cheers,
>>> 
>>> Dave.
>> 
>> you was right.
>> There was new kernel built. /usr/src/linux pointed to new kernel 
>> source.
>> But machine was not rebooted. So kernel version before kernel built 
>> was loaded.
>> I rebooted machine.
>> i renoved logical volume
>> i created logical volume
> 
> Hope it landed back in the same place!
> 
>> i tried to mount it and get:
>> 
>> Aug 25 18:43:15 backupserver kernel: md4: unknown partition table
>> Aug 25 18:43:15 backupserver syslog-ng[1417]: Internal error, 
>> alarm_set() called while an alarm is still active;
>> Aug 25 18:43:56 backupserver kernel: md4: unknown partition table
>> Aug 25 18:44:01 backupserver kernel: XFS (dm-2): Invalid superblock 
>> magic number
>> 
>> 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"

marko




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

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

Re: Cant mount xfs lvm. Experimental Features?

[Eric Sandeen]

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

Re: Cant mount xfs lvm. Experimental Features?

[Marko Weber|8000]

hi eric,

Am 2015-08-25 20:18, schrieb Eric Sandeen:
> On 8/25/15 11:51 AM, Marko Weber|8000 wrote:
>> 
>> dave,
>> 
>> Am 2015-08-25 13:54, schrieb Dave Chinner:
>>> On Tue, Aug 25, 2015 at 10:25:16AM +0200, Marko Weber|8000 wrote:
>>>> 
>>>> Hello List, Hello Dave...
>>>> 
>>>> 
>>>> i try to mount on my backup server an Lvm Partition and get errors
>>>> in stdout and log:
>>>> 
>>>> /var/log/messages:
>>>> 
>>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Version 5
>>>> superblock detected. This kernel has EXPERIMENTAL support enabled!
>>>> Aug 25 10:20:31 backupserver kernel: Use of these features in this
>>>> kernel is at your own risk!
>>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Superblock has
>>>> unknown read-only compatible features (0x1) enabled.
>>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Attempted to mount
>>>> read-only compatible filesystem read-write.
>>>> Aug 25 10:20:31 backupserver kernel: Filesystem can only be safely
>>>> mounted read only.
>>>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): SB validate failed
>>>> with error 22.
>>> 
>>> You need to run the same version kernel on both servers. The primary
>>> has a more recent kernel and feature set than your older backup
>>> server is running.
>>> 
>>> Cheers,
>>> 
>>> Dave.
>> 
>> you was right.
>> There was new kernel built. /usr/src/linux pointed to new kernel 
>> source.
>> But machine was not rebooted. So kernel version before kernel built 
>> was loaded.
>> I rebooted machine.
>> i renoved logical volume
>> i created logical volume
> 
> Hope it landed back in the same place!
> 
>> i tried to mount it and get:
>> 
>> Aug 25 18:43:15 backupserver kernel: md4: unknown partition table
>> Aug 25 18:43:15 backupserver syslog-ng[1417]: Internal error, 
>> alarm_set() called while an alarm is still active;
>> Aug 25 18:43:56 backupserver kernel: md4: unknown partition table
>> Aug 25 18:44:01 backupserver kernel: XFS (dm-2): Invalid superblock 
>> magic number
>> 
>> 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.

eric,
i rebootet the machine and created a new logical volume.
i formatted the lv with mkfs.xfs
i tried to mount it on the new kernel:

Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Version 5 superblock 
detected. This kernel has EXPERIMENTAL support enabled!
Aug 26 00:47:17 backupserver kernel: Use of these features in this 
kernel is at your own risk!
Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Superblock has unknown 
read-only compatible features (0x1) enabled.
Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Attempted to mount 
read-only compatible filesystem read-write.
Aug 26 00:47:17 backupserver kernel: Filesystem can only be safely 
mounted read only.
Aug 26 00:47:17 backupserver kernel: XFS (dm-2): SB validate failed with 
error 22.


this happens with the newly created logical volume.

the other 2 lvm partitions with xfs are fine.

any idea?

marko








> 
> -Eric

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

Re: Cant mount xfs lvm. Experimental Features?

[Eric Sandeen]

On 8/25/15 5:53 PM, Marko Weber|8000 wrote:

> eric,
> i rebootet the machine and created a new logical volume.
> i formatted the lv with mkfs.xfs
> i tried to mount it on the new kernel:
> 
> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Version 5 superblock detected. This kernel has EXPERIMENTAL support enabled!
> Aug 26 00:47:17 backupserver kernel: Use of these features in this kernel is at your own risk!
> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Superblock has unknown read-only compatible features (0x1) enabled.
> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Attempted to mount read-only compatible filesystem read-write.
> Aug 26 00:47:17 backupserver kernel: Filesystem can only be safely mounted read only.
> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): SB validate failed with error 22.

http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F ...

> this happens with the newly created logical volume.
> 
> the other 2 lvm partitions with xfs are fine.
> 
> any idea?

Without any actual information (i.e. kernel versions or userspace version),
I'll have to assume that you have recent xfsprogs which sets some features by
default which older kernels cannot understand.

> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Superblock has unknown read-only compatible features (0x1) enabled.

#define XFS_SB_FEAT_RO_COMPAT_FINOBT   (1 << 0)         /* free inode btree */

mkfs.xfs with -m crc=0,finobt=0 to turn off these features if you have an older kernel which
doesn't understand them.

-Eric

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

Re: Cant mount xfs lvm. Experimental Features?

[Marko Weber|8000]

Am 2015-08-26 00:58, schrieb Eric Sandeen:
> On 8/25/15 5:53 PM, Marko Weber|8000 wrote:
> 
>> eric,
>> i rebootet the machine and created a new logical volume.
>> i formatted the lv with mkfs.xfs
>> i tried to mount it on the new kernel:
>> 
>> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Version 5 superblock 
>> detected. This kernel has EXPERIMENTAL support enabled!
>> Aug 26 00:47:17 backupserver kernel: Use of these features in this 
>> kernel is at your own risk!
>> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Superblock has 
>> unknown read-only compatible features (0x1) enabled.
>> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Attempted to mount 
>> read-only compatible filesystem read-write.
>> Aug 26 00:47:17 backupserver kernel: Filesystem can only be safely 
>> mounted read only.
>> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): SB validate failed 
>> with error 22.
> l
> http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> ...
> 
>> this happens with the newly created logical volume.
>> 
>> the other 2 lvm partitions with xfs are fine.
>> 
>> any idea?
> 
> Without any actual information (i.e. kernel versions or userspace 
> version),
> I'll have to assume that you have recent xfsprogs which sets some 
> features by
> default which older kernels cannot understand.

ok, what info do you need?

on gentoo-linux:

xfsprogs: v 3.2.4 (Useflag, nls readline)
kernel:   3.14.51


> 
>> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Superblock has 
>> unknown read-only compatible features (0x1) enabled.
> 
> #define XFS_SB_FEAT_RO_COMPAT_FINOBT   (1 << 0)         /* free inode 
> btree */
> 
> mkfs.xfs with -m crc=0,finobt=0 to turn off these features if you have
> an older kernel which
> doesn't understand them.
> 
> -Eric

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

Re: Cant mount xfs lvm. Experimental Features?

[Dave Chinner]

On Wed, Aug 26, 2015 at 01:02:58AM +0200, Marko Weber|8000 wrote:
> Am 2015-08-26 00:58, schrieb Eric Sandeen:
> >On 8/25/15 5:53 PM, Marko Weber|8000 wrote:
> >
> >>eric,
> >>i rebootet the machine and created a new logical volume.
> >>i formatted the lv with mkfs.xfs
> >>i tried to mount it on the new kernel:
> >>
> >>Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Version 5
> >>superblock detected. This kernel has EXPERIMENTAL support
> >>enabled!
> >>Aug 26 00:47:17 backupserver kernel: Use of these features in
> >>this kernel is at your own risk!
> >>Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Superblock has
> >>unknown read-only compatible features (0x1) enabled.
> >>Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Attempted to
> >>mount read-only compatible filesystem read-write.
> >>Aug 26 00:47:17 backupserver kernel: Filesystem can only be
> >>safely mounted read only.
> >>Aug 26 00:47:17 backupserver kernel: XFS (dm-2): SB validate
> >>failed with error 22.
> >l
> >http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> >...
> >
> >>this happens with the newly created logical volume.
> >>
> >>the other 2 lvm partitions with xfs are fine.
> >>
> >>any idea?
> >
> >Without any actual information (i.e. kernel versions or userspace
> >version),
> >I'll have to assume that you have recent xfsprogs which sets some
> >features by
> >default which older kernels cannot understand.
> 
> ok, what info do you need?
> 
> on gentoo-linux:
> 
> xfsprogs: v 3.2.4 (Useflag, nls readline)
> kernel:   3.14.51

Kernel is too old for finobt=1, and really too old for CRCs to be
enabled (not fully supported until 3.16).

So, either:

> >mkfs.xfs with -m crc=0,finobt=0 to turn off these features if you have
> >an older kernel which
> >doesn't understand them.

or upgrade your kernel.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

Re: Cant mount xfs lvm. Experimental Features?

[Dave Chinner]

On Wed, Aug 26, 2015 at 12:53:51AM +0200, Marko Weber|8000 wrote:
[....]
> i rebootet the machine and created a new logical volume.
> i formatted the lv with mkfs.xfs
> i tried to mount it on the new kernel:
> 
> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Version 5
> superblock detected. This kernel has EXPERIMENTAL support enabled!
> Aug 26 00:47:17 backupserver kernel: Use of these features in this
> kernel is at your own risk!
> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Superblock has
> unknown read-only compatible features (0x1) enabled.
> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Attempted to mount
> read-only compatible filesystem read-write.
> Aug 26 00:47:17 backupserver kernel: Filesystem can only be safely
> mounted read only.
> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): SB validate failed
> with error 22.
> 
> 
> this happens with the newly created logical volume.
> 
> the other 2 lvm partitions with xfs are fine.
> 
> any idea?

Clearly you have a kernel too old to read the on-disk format that
mkfs.xfs has written - as I pointed out originally.

Would you please tell us what the versions of the kernels
you are using, as well as the mkfs.xfs version?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

Re: Cant mount xfs lvm. Experimental Features?

[Marko Weber|8000]

Am 2015-08-26 01:03, schrieb Dave Chinner:
> On Wed, Aug 26, 2015 at 12:53:51AM +0200, Marko Weber|8000 wrote:
> [....]
>> i rebootet the machine and created a new logical volume.
>> i formatted the lv with mkfs.xfs
>> i tried to mount it on the new kernel:
>> 
>> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Version 5
>> superblock detected. This kernel has EXPERIMENTAL support enabled!
>> Aug 26 00:47:17 backupserver kernel: Use of these features in this
>> kernel is at your own risk!
>> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Superblock has
>> unknown read-only compatible features (0x1) enabled.
>> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Attempted to mount
>> read-only compatible filesystem read-write.
>> Aug 26 00:47:17 backupserver kernel: Filesystem can only be safely
>> mounted read only.
>> Aug 26 00:47:17 backupserver kernel: XFS (dm-2): SB validate failed
>> with error 22.
>> 
>> 
>> this happens with the newly created logical volume.
>> 
>> the other 2 lvm partitions with xfs are fine.
>> 
>> any idea?
> 
> Clearly you have a kernel too old to read the on-disk format that
> mkfs.xfs has written - as I pointed out originally.
> 
> Would you please tell us what the versions of the kernels
> you are using, as well as the mkfs.xfs version?

Kernel vanilla-sources 3.14.51 (longterm support)
xfs-progs 3.2.4 (gentoo)
mkfs.xfs 3.2.4

AND HEY!  Eric, your hint worked:

backupserver ~ # mkfs.xfs -f -m crc=0,finobt=0 /dev/VolGroup01/vmstore
meta-data=/dev/VolGroup01/vmstore isize=256    agcount=4, 
agsize=19660800 blks
          =                       sectsz=4096  attr=2, projid32bit=1
          =                       crc=0        finobt=0
data     =                       bsize=4096   blocks=78643200, 
imaxpct=25
          =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal log           bsize=4096   blocks=38400, version=2
          =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
backupserver ~ # mount /dev/VolGroup01/vmstore /var/storage01/
backupserver ~ # df -h
Filesystem                      Size  Used Avail Use% Mounted on
/dev/root                        35G   21G   15G  60% /
devtmpfs                         10M     0   10M   0% /dev
tmpfs                           1.6G  464K  1.6G   1% /run
shm                             7.7G   72K  7.7G   1% /dev/shm
cgroup_root                      10M     0   10M   0% /sys/fs/cgroup
/dev/mapper/VolGroup01-backup   500G  396G  105G  80% 
/var/volgroup01/backup
/dev/mapper/VolGroup01-dumps    200G   89G  112G  45% /var/dumps
/dev/mapper/VolGroup01-vmstore  300G   33M  300G   1% /var/storage01



dave, so the latest lts kernel 3.14.51 does not support to mount lvm2 
partitions formatted with mkfs.xfs 3.2.4?


marko


> 
> Cheers,
> 
> Dave.

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

Re: Cant mount xfs lvm. Experimental Features?

[Dave Chinner]

On Wed, Aug 26, 2015 at 01:10:41AM +0200, Marko Weber|8000 wrote:
> dave, so the latest lts kernel 3.14.51 does not support to mount
> lvm2 partitions formatted with mkfs.xfs 3.2.4?

As we've always done in the past, we've waited for around a year
after upstream kernel support for a feature has been supported
before turning on the feature by default in xfsprogs. Kernel 3.16
was released just over a year ago with full CRC support. Our hand
was kinda forced by distros independently enabling these features by
default before upstream enabled them, so we enabled it a bt sooner
than previous feature default changes.

Clearly we (upstream) have no control over what distros ship and
enable. We can't stop distros from upgrading userspace out of step
with the kernel they ship, nor can we stop them from changing
default feature enablement. However, it's up to the distro to make
sure that the userspace package and the default configurations they
ship work correctly with the kernel they ship.

i.e. if Gentoo are shipping xfsprogs 3.2.4 w/ kernel 3.14.51, then
Gentoo has a quality control problem - they have failed to verify
that the packages they are shipping work correctly before shipping
them to users...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

Re: Cant mount xfs lvm. Experimental Features?

[Marko Weber|8000]

dave,

Am 2015-08-26 01:33, schrieb Dave Chinner:
> On Wed, Aug 26, 2015 at 01:10:41AM +0200, Marko Weber|8000 wrote:
>> dave, so the latest lts kernel 3.14.51 does not support to mount
>> lvm2 partitions formatted with mkfs.xfs 3.2.4?
> 
> As we've always done in the past, we've waited for around a year
> after upstream kernel support for a feature has been supported
> before turning on the feature by default in xfsprogs. Kernel 3.16
> was released just over a year ago with full CRC support. Our hand
> was kinda forced by distros independently enabling these features by
> default before upstream enabled them, so we enabled it a bt sooner
> than previous feature default changes.
> 
> Clearly we (upstream) have no control over what distros ship and
> enable. We can't stop distros from upgrading userspace out of step
> with the kernel they ship, nor can we stop them from changing
> default feature enablement. However, it's up to the distro to make
> sure that the userspace package and the default configurations they
> ship work correctly with the kernel they ship.
> 
> i.e. if Gentoo are shipping xfsprogs 3.2.4 w/ kernel 3.14.51, then
> Gentoo has a quality control problem - they have failed to verify
> that the packages they are shipping work correctly before shipping
> them to users...
> 
> Cheers,
> 
> Dave.

just want to report that with vanilla-kernel 3.18.19 all is fine again.

marko

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