finest and rhel/centos 7.1

finest and rhel/centos 7.1

[Charles Weber]

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

Hi everyone,
I am building a large storage server and noticed to my delight that mkfs.xfs in 7.1 now supports finobts=1. But I get mount errors saying below. Since the FS in question mount fine so long as I don’t specify finobts=1 while formatting, should I assume the rest of 7.1 is not yet ready for it? Or is there some option I missed?

thanks,
Chuck
xfsprogs-3.2.1-6.el7.x86_64
kernel-3.10.0-229.1.2.el7.x86_64
[75881.037768] SELinux: initialized (dev dm-7, type xfs), uses xattr
[75908.498994] XFS (dm-7): Superblock has unknown read-only compatible features (0x1) enabled.
[75908.499035] XFS (dm-7): Attempted to mount read-only compatible filesystem read-write.
Filesystem can only be safely mounted read only.
[75908.499058] XFS (dm-7): SB validate failed with error 22.


[root@NIAIRPGL1 share]# modinfo xfs
filename:       /lib/modules/3.10.0-229.1.2.el7.x86_64/kernel/fs/xfs/xfs.ko
license:        GPL
description:    SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
author:         Silicon Graphics, Inc.
alias:          fs-xfs
rhelversion:    7.1
srcversion:     3E3940432E169BEE955EDE9
depends:        libcrc32c
intree:         Y
vermagic:       3.10.0-229.1.2.el7.x86_64 SMP mod_unload modversions 
signer:         CentOS Linux kernel signing key
sig_key:        34:B5:BC:A2:B7:06:D8:2E:72:A5:BE:3E:E4:09:BE:C7:19:5E:A5:08
sig_hashalgo:   sha256


[-- Attachment #1.2: Type: text/html, Size: 3959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

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

Re: finest and rhel/centos 7.1

[Eric Sandeen]

On 4/7/15 10:30 AM, Charles Weber wrote:
> Hi everyone, I am building a large storage server and noticed to my
> delight that mkfs.xfs in 7.1 now supports finobts=1. But I get mount
> errors saying below. Since the FS in question mount fine so long as I
> don’t specify finobts=1 while formatting, should I assume the rest of
> 7.1 is not yet ready for it? Or is there some option I missed?

That was a bit of an oversight.

finobt will be available kernelside eventually, but userspace
jumped the gun.

-Eric
 
> thanks, Chuck *xfs*progs-3.2.1-6.el7.x86_64 
> kernel-3.10.0-229.1.2.el7.x86_64 [75881.037768] SELinux: initialized
> (dev dm-7, type xfs), uses xattr [75908.498994] XFS (dm-7):
> Superblock has unknown read-only compatible features (0x1) enabled. 
> [75908.499035] XFS (dm-7): Attempted to mount read-only compatible
> filesystem read-write. Filesystem can only be safely mounted read
> only. [75908.499058] XFS (dm-7): SB validate failed with error 22.
> 
> 
> [root@NIAIRPGL1 share]# modinfo xfs filename:
> /lib/modules/3.10.0-229.1.2.el7.x86_64/kernel/fs/xfs/xfs.ko license:
> GPL description:    SGI XFS with ACLs, security attributes, large
> block/inode numbers, no debug enabled author:         Silicon
> Graphics, Inc. alias:          fs-xfs rhelversion:    7.1 srcversion:
> 3E3940432E169BEE955EDE9 depends:        libcrc32c intree:         Y 
> vermagic:       3.10.0-229.1.2.el7.x86_64 SMP mod_unload modversions
>  signer:         CentOS Linux kernel signing key sig_key:
> 34:B5:BC:A2:B7:06:D8:2E:72:A5:BE:3E:E4:09:BE:C7:19:5E:A5:08 
> sig_hashalgo:   sha256
> 
> 
> 
> _______________________________________________ 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