All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "LinuxAdmin.pl - administracja serwerami Linux" <info@linuxadmin.pl>
Cc: Eric Sandeen <sandeen@sandeen.net>, linux-xfs@vger.kernel.org
Subject: Re: xfs_info: no info about XFS version?
Date: Thu, 10 Sep 2020 21:46:53 -0700	[thread overview]
Message-ID: <20200911044653.GS7955@magnolia> (raw)
In-Reply-To: <57839a674d8b54baafa40d2b002e19b5@linuxadmin.pl>

On Fri, Sep 11, 2020 at 06:14:09AM +0200, LinuxAdmin.pl - administracja serwerami Linux wrote:
> W dniu 2020-09-10 22:44, Eric Sandeen napisał(a):
> > On 9/10/20 3:26 PM, LinuxAdmin.pl - administracja serwerami Linux wrote:
> > > 
> > > Hello,
> > > 
> > > why there is no info about XFS version on xfs_info?
> > 
> > Yeah, this is confusing.
> > 
> > TBH I think "V4" vs "V5" is a secret developer handshake.  Admins know
> > this as "not-crc-enabled" vs "crc-enabled"
> > 
> > Below is a V4 filesystem, due to crc=0
> 
> That's the point! How you will be determining the version number in V7?
> crc=3 xyz=0 abc=1?
> I know that is V4 (migration to V5 already planned!) but thinking the human
> way - it will be nice to have a simple info of used version :)

Seeing as most software goes downhill after V5 (Word, Windows, Notes...)
we intend to beat the averages by never introducing a V6, and expanding
the feature flags fields instead.

--D

> > -Eric
> > 
> > > # LANG=en_US.UTF-8 xfs_info /dev/sdb1
> > > meta-data=/dev/sdb1              isize=256    agcount=4,
> > > agsize=6553408 blks
> > >          =                       sectsz=512   attr=2, projid32bit=0
> > >          =                       crc=0        finobt=0, sparse=0,
> > > rmapbt=0
> > >          =                       reflink=0
> > > data     =                       bsize=4096   blocks=26213632,
> > > imaxpct=25
> > >          =                       sunit=0      swidth=0 blks
> > > naming   =version 2              bsize=4096   ascii-ci=0, ftype=0
> > > log      =internal log           bsize=4096   blocks=12799, version=2
> > >          =                       sectsz=512   sunit=0 blks,
> > > lazy-count=1
> > > realtime =none                   extsz=4096   blocks=0, rtextents=0
> > > 
> 
> -- 
> LinuxAdmin.pl - administracja serwerami Linux
> Wojciech Błaszkowski
> +48 600 197 207

      reply	other threads:[~2020-09-11  4:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 20:26 xfs_info: no info about XFS version? LinuxAdmin.pl - administracja serwerami Linux
2020-09-10 20:44 ` Eric Sandeen
2020-09-11  4:14   ` LinuxAdmin.pl - administracja serwerami Linux
2020-09-11  4:46     ` Darrick J. Wong [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=20200911044653.GS7955@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=info@linuxadmin.pl \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.