From: Dave Chinner <david@fromorbit.com>
To: Gabriel VLASIU <gabriel@vlasiu.net>
Cc: xfs@oss.sgi.com
Subject: Re: failed to set versionnum in AG 1
Date: Mon, 5 Mar 2012 12:10:32 +1100 [thread overview]
Message-ID: <20120305011032.GL5091@dastard> (raw)
In-Reply-To: <alpine.LRH.2.02.1203041803340.8964@mail.vlasiu.net>
On Sun, Mar 04, 2012 at 06:09:12PM +0200, Gabriel VLASIU wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi!
>
> On all my older partitions with xfs I have this problem:
>
> # xfs_db -x /dev/sdh1
> xfs_db> version
> versionnum [0xb4b4+0x8] = V4,ATTR,NLINK,ALIGN,DIRV2,LOGV2,EXTFLG,MOREBITS,ATTR2
it already has the attr2 feature bit set.
> xfs_db> version attr2
> writing all SBs
> Superblock has mismatched features2 fields, skipping modification
> failed to set versionnum in AG 1
> versionnum [0xb4b4+0x8] = V4,ATTR,NLINK,ALIGN,DIRV2,LOGV2,EXTFLG,MOREBITS,ATTR2
What version of xfs_db are you using?
And why do you need to set the attr2 feature this way? It gets set
automatically when it gets used because on recent kernels it is the
default mount option. If you have an older kernel and need to turn
attr2 on, then simply add the "attr2" field to the mount options on
the filesystem. Once xfs_info reports attr=2 for the filesytem, you
can remove the attr2 mount option...
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:[~2012-03-05 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 16:09 failed to set versionnum in AG 1 Gabriel VLASIU
2012-03-05 1:10 ` Dave Chinner [this message]
2012-03-05 7:31 ` Gabriel VLASIU
2012-03-05 22:28 ` Dave Chinner
2012-03-06 7:30 ` Gabriel VLASIU
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=20120305011032.GL5091@dastard \
--to=david@fromorbit.com \
--cc=gabriel@vlasiu.net \
--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