From: Dave Chinner <david@fromorbit.com>
To: "L.A. Walsh" <xfs@tlinx.org>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: why crc req on free-inobt & file-type-indir options?
Date: Sat, 8 Aug 2015 08:55:31 +1000 [thread overview]
Message-ID: <20150807225531.GG3902@dastard> (raw)
In-Reply-To: <55C468F0.2040707@tlinx.org>
On Fri, Aug 07, 2015 at 01:14:40AM -0700, L.A. Walsh wrote:
> >On 8/6/15 7:52 PM, L.A. Walsh wrote:
> >>Example:
> >>sudo mkfs-xfs-raid SCR /dev/mapper/Data-Home2
> >>mkfs.xfs -mcrc=1,finobt=1 -i maxpct=5,size=512 -l size=32752b,lazy-count=1 -d su=64k,sw=4 -s size=4096 -L SCR -f /dev/mapper/Data-Home2
> >>meta-data=/dev/mapper/Data-Home2 isize=512 agcount=32, agsize=12582896 blks
> >> = sectsz=4096 attr=2, projid32bit=1
> >> = crc=1 finobt=1
> >>data = bsize=4096 blocks=402652672, imaxpct=5
> >> = sunit=16 swidth=64 blks
> >>naming =version 2 bsize=4096 ascii-ci=0 ftype=1
> >>log =internal log bsize=4096 blocks=32752, version=2
> >> = sectsz=4096 sunit=1 blks, lazy-count=1
> >>realtime =none extsz=4096 blocks=0, rtextents=0
> >
> >ok...
> >
> >>xfs_admin: WARNING - filesystem uses v1 dirs,limited functionality provided.
> >
> >Um, what? What xfs_admin command generated this? With what xfsprogs version?
> >/usr/sbin/xfs_admin -V
> xfs_admin version 3.1.11
> ---
The above error message is what old versions of xfs_db emit when
they see a filesystem version they don't understand.
xfsprogs 3.1.11 doesn't support CRCs. 3.2.0 was the first version of
xfsprogs to support CRCs, and 3.2.1 (IIRC) was the first to support
finobt, so the make binary came from a different build to the xfs_db
binary that xfs_admin executes.
Can you please ensure that you are running an up-to-date xfsprogs
and not some mix-and-match of different versions with differing
feature support capabilities?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-08-07 22:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 2:52 why crc req on free-inobt & file-type-indir options? L.A. Walsh
2015-08-07 5:00 ` Eric Sandeen
2015-08-07 8:14 ` L.A. Walsh
2015-08-07 17:01 ` Eric Sandeen
2015-08-07 22:55 ` Dave Chinner [this message]
2015-08-08 0:50 ` L.A. Walsh
2015-08-08 1:45 ` Eric Sandeen
2015-08-08 2:59 ` L.A. Walsh
2015-08-09 0:11 ` Dave Chinner
2015-08-13 0:24 ` L.A. Walsh
2015-08-07 8:17 ` L.A. Walsh
2015-08-07 5:36 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2015-08-07 2:53 L.A. Walsh
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=20150807225531.GG3902@dastard \
--to=david@fromorbit.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.org \
/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