public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Patrick Emblen <support@talbragar.com.au>, 694624@bugs.debian.org
Cc: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#694624: /usr/sbin/xfs_freeze: freezes under lying (root) filesystem if mountpoint is not currently mounted
Date: Fri, 30 Nov 2012 11:04:42 -0500	[thread overview]
Message-ID: <20121130160442.GB5667@infradead.org> (raw)
In-Reply-To: <20121128134342.4359.51203.reportbug@t5>

It probably makes sense to only allow it for mountpoints, then again
I fear people might already be using it differently in existing scripts.

Maybe be should add an -s / --strict option that forces it to only work
on mountpoints?

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2012-11-30 17:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 13:43 Bug#694624: /usr/sbin/xfs_freeze: freezes under lying (root) filesystem if mountpoint is not currently mounted Patrick Emblen
2012-11-30 16:04 ` Christoph Hellwig [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=20121130160442.GB5667@infradead.org \
    --to=hch@infradead.org \
    --cc=694624@bugs.debian.org \
    --cc=submit@bugs.debian.org \
    --cc=support@talbragar.com.au \
    /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