public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 206429] xfs_admin can't print both label and UUID for mounted filesystems
Date: Wed, 05 Feb 2020 15:39:51 +0000	[thread overview]
Message-ID: <bug-206429-201763-gudvBTA8SF@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206429-201763@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=206429

Eric Sandeen (sandeen@sandeen.net) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sandeen@sandeen.net

--- Comment #1 from Eric Sandeen (sandeen@sandeen.net) ---
The patch is not quite the right approach - the get label command sets both
DB_OPTS and IO_OPTS, as does the set label command, and your patch would make
it fall back to xfs_db for both, which will then fail to set a label on a
mounted filesystem:

# db/xfs_admin.sh -L foobar mnt
xfs_admin: cannot open mnt: Is a directory

# sh -x db/xfs_admin.sh -L foobar mnt
...
+ eval xfs_db -x -p xfs_admin -c ''\''label' 'foobar'\''' mnt
++ xfs_db -x -p xfs_admin -c 'label foobar' mnt
xfs_admin: cannot open mnt: Is a directory

xfs_admin has become convoluted/complicated, let me give this some thought.

Thanks for the report,

-Eric

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      reply	other threads:[~2020-02-05 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 12:28 [Bug 206429] New: xfs_admin can't print both label and UUID for mounted filesystems bugzilla-daemon
2020-02-05 15:39 ` bugzilla-daemon [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=bug-206429-201763-gudvBTA8SF@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@vger.kernel.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