From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id 7D9AB7F6D for ; Tue, 7 Apr 2015 10:30:52 -0500 (CDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by relay1.corp.sgi.com (Postfix) with ESMTP id 6D9698F8033 for ; Tue, 7 Apr 2015 08:30:49 -0700 (PDT) Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by cuda.sgi.com with ESMTP id WxOOSYS665cfj4F5 (version=TLSv1 cipher=RC4-SHA bits=128 verify=NO) for ; Tue, 07 Apr 2015 08:30:48 -0700 (PDT) Received: by qcgx3 with SMTP id x3so22418456qcg.3 for ; Tue, 07 Apr 2015 08:30:47 -0700 (PDT) Received: from [156.40.66.13] ([156.40.66.13]) by mx.google.com with ESMTPSA id 132sm5564523qhf.17.2015.04.07.08.30.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Apr 2015 08:30:46 -0700 (PDT) From: Charles Weber Subject: finest and rhel/centos 7.1 Message-Id: <014A8EAA-D469-49D9-9A80-5C4CC455C74E@gmail.com> Date: Tue, 7 Apr 2015 11:30:44 -0400 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1899210073654739769==" Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: xfs@oss.sgi.com --===============1899210073654739769== Content-Type: multipart/alternative; boundary="Apple-Mail=_BB0CDBE2-B5F6-4E28-8A42-1682D2F0A756" --Apple-Mail=_BB0CDBE2-B5F6-4E28-8A42-1682D2F0A756 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi everyone, I am building a large storage server and noticed to my delight that = mkfs.xfs in 7.1 now supports finobts=3D1. But I get mount errors saying = below. Since the FS in question mount fine so long as I don=E2=80=99t = specify finobts=3D1 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=20 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 --Apple-Mail=_BB0CDBE2-B5F6-4E28-8A42-1682D2F0A756 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi everyone,

I am building a large storage = server and noticed to my delight that mkfs.xfs in 7.1 now supports = finobts=3D1. But I get mount errors saying below. Since the FS in = question mount fine so long as I don=E2=80=99t specify finobts=3D1 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

= --Apple-Mail=_BB0CDBE2-B5F6-4E28-8A42-1682D2F0A756-- --===============1899210073654739769== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs --===============1899210073654739769==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id 5B6F87F6D for ; Tue, 7 Apr 2015 10:34:11 -0500 (CDT) Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by relay3.corp.sgi.com (Postfix) with ESMTP id DDDD6AC003 for ; Tue, 7 Apr 2015 08:34:07 -0700 (PDT) Received: from sandeen.net (sandeen.net [63.231.237.45]) by cuda.sgi.com with ESMTP id Zaw40kRNNwZxGuQU for ; Tue, 07 Apr 2015 08:34:06 -0700 (PDT) Message-ID: <5523F8ED.1060105@sandeen.net> Date: Tue, 07 Apr 2015 10:34:05 -0500 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: finest and rhel/centos 7.1 References: <014A8EAA-D469-49D9-9A80-5C4CC455C74E@gmail.com> In-Reply-To: <014A8EAA-D469-49D9-9A80-5C4CC455C74E@gmail.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Charles Weber , xfs@oss.sgi.com 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=3D1. But I get mount > errors saying below. Since the FS in question mount fine so long as I > don=92t specify finobts=3D1 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