public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Charles Weber <chaweber@gmail.com>, xfs@oss.sgi.com
Subject: Re: finest and rhel/centos 7.1
Date: Tue, 07 Apr 2015 10:34:05 -0500	[thread overview]
Message-ID: <5523F8ED.1060105@sandeen.net> (raw)
In-Reply-To: <014A8EAA-D469-49D9-9A80-5C4CC455C74E@gmail.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=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

      reply	other threads:[~2015-04-07 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 15:30 finest and rhel/centos 7.1 Charles Weber
2015-04-07 15:34 ` Eric Sandeen [this message]

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=5523F8ED.1060105@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=chaweber@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox