public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: sandeen@redhat.com, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 8/9] xfs_info: call xfs_db for offline filesystems
Date: Thu, 3 May 2018 14:55:54 -0700	[thread overview]
Message-ID: <20180503215554.GE26569@magnolia> (raw)
In-Reply-To: <e7dea090-ae58-d3d8-c9d0-33917e993d16@sandeen.net>

On Thu, May 03, 2018 at 04:22:24PM -0500, Eric Sandeen wrote:
> On 4/17/18 9:46 PM, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> > 
> > If the online filesystem geometry query doesn't work, try using xfs_db
> > to see if we can grab the information offline.
> > 
> 
> I'm slightly concerned that having all-singing, all-dancing tools
> that operate on mounted, unmounted, devices, mountpoints, and images
> will further encourage people to think that operations on mounted
> block devices are Just Fine(tm).

<nod> The current semantics of xfs_info are that one has to feed it a
mountpoint, which means the arg is a direct... oh dangit.

# touch mugga
# mount /bin/true mugga --bind
# xfs_info ./mugga 
meta-data=/dev/mapper/system-root isize=512    agcount=4, agsize=1953024 blks

Uh, ok, so the new behavior of xfs_info is that if you pass it a block
device or a file it'll try to call xfs_db (assuming it's a fs, fs image
file, or I guess future-dchinner subvolume); and if it's any other kind
of fs object it'll try spaceman (which requires a mountpoint arg).

Hopefully that's ok with Dave's subvol plans?

> But ... I suppose the convenience is worth it.
> 
> ...
> 
> > diff --git a/man/man8/xfs_info.8 b/man/man8/xfs_info.8
> > new file mode 100644
> > index 0000000..c4c470d
> > --- /dev/null
> > +++ b/man/man8/xfs_info.8
> > @@ -0,0 +1,95 @@
> > +.\" Verbatim blocks taken from openssl req manpage content
> > +.de Vb \" Begin verbatim text
> > +.ft CW
> > +.nf
> > +.ne \\$1
> > +..
> > +.de Ve \" End verbatim text
> > +.ft R
> > +.fi
> > +..
> > +
> > +.TH xfs_info 8
> > +.SH NAME
> > +xfs_info, \- display XFS filesystem geometry information
> 
> drop the comma pls, or I can do this.

I'll drop it in my patches, though if you don't find any serious
problems that warrant a reissue then you should do it.

> ...
> 
> > +.BR \-V .
> > +.SH "EXAMPLES"
> > +
> > +Understanding xfs_info output.
> > +.PP
> > +Suppose one has the following "xfs_info /dev/sda" output:
> > +.PP
> > +.RS 2
> > +.Vb
> > +\&meta-data=/dev/sda      isize=256    agcount=32, agsize=16777184 blks
> > +\&         =              sectsz=512   attr=2
> > +\&data     =              bsize=4096   blocks=536869888, imaxpct=5
> > +\&         =              sunit=32     swidth=128 blks
> > +\&naming   =version 2     bsize=4096
> > +\&log      =internal log  bsize=4096   blocks=32768, version=2
> > +\&         =              sectsz=512   sunit=32 blks, lazy-count=1
> > +\&realtime =none          extsz=524288 blocks=0, rtextents=0
> > +.Ve
> 
> Should we update this to a more modern version?  *shrug*

Yeah probably.

--D

> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-05-03 21:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18  2:45 [PATCH 0/9] xfsprogs-4.17: geometry refactoring Darrick J. Wong
2018-04-18  2:45 ` [PATCH 1/9] libfrog: move platform specific runtime support code out of libxfs Darrick J. Wong
2018-05-03 18:23   ` Eric Sandeen
2018-04-18  2:45 ` [PATCH 2/9] libfrog: refactor fs geometry printing function Darrick J. Wong
2018-05-03 18:47   ` Eric Sandeen
2018-05-03 21:27   ` Eric Sandeen
2018-05-03 21:35     ` Darrick J. Wong
2018-04-18  2:45 ` [PATCH 3/9] mkfs: use geometry generation / helper functions Darrick J. Wong
2018-05-03 18:52   ` Eric Sandeen
2018-04-18  2:45 ` [PATCH 4/9] xfs_db: add a superblock info command Darrick J. Wong
2018-05-03 20:53   ` Eric Sandeen
2018-05-03 21:44     ` Darrick J. Wong
2018-05-23  3:30   ` [PATCH v2 " Darrick J. Wong
2018-05-23  3:57     ` Allison Henderson
2018-04-18  2:46 ` [PATCH 5/9] xfs_spaceman: print a nicer message when the file path isn't on an xfs Darrick J. Wong
2018-05-03 20:57   ` Eric Sandeen
2018-05-23  3:31   ` [PATCH v2 " Darrick J. Wong
2018-05-23  3:58     ` Allison Henderson
2018-04-18  2:46 ` [PATCH 6/9] xfs_spaceman: add a superblock info command Darrick J. Wong
2018-05-03 21:09   ` Eric Sandeen
2018-05-03 21:39     ` Darrick J. Wong
2018-05-08 15:24       ` Darrick J. Wong
2018-05-23  3:32   ` [PATCH v2 " Darrick J. Wong
2018-05-23  4:08     ` Allison Henderson
2018-04-18  2:46 ` [PATCH 7/9] xfs_info: move to xfs_spaceman Darrick J. Wong
2018-05-03 21:17   ` Eric Sandeen
2018-05-03 21:48     ` Darrick J. Wong
2018-04-18  2:46 ` [PATCH 8/9] xfs_info: call xfs_db for offline filesystems Darrick J. Wong
2018-05-03 21:22   ` Eric Sandeen
2018-05-03 21:55     ` Darrick J. Wong [this message]
2018-05-23  3:33   ` [PATCH v2 " Darrick J. Wong
2018-05-23  4:36     ` Allison Henderson
2018-04-18  2:46 ` [PATCH 9/9] xfs_growfs: refactor geometry reporting Darrick J. Wong
2018-05-03 21:25   ` Eric Sandeen

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=20180503215554.GE26569@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox