public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Pat Emblen <support@talbragar.com.au>
To: 694624@bugs.debian.org
Subject: Bug#694624: /usr/sbin/xfs_freeze: freezes under lying (root)
Date: Tue, 04 Dec 2012 10:53:56 +1100	[thread overview]
Message-ID: <50BD3B94.4070505@talbragar.com.au> (raw)

 > If you are running scripts remotely and they don't handle errors
 > properly, then that's your problem....

OK, can you then fix the man page to describe the real behaviour of the
program so that users have a chance to intelligently decide what error
checking to do in their scripts.
I.E the argument isn't a mount point, it's a path, and perhaps use
'filesystem' rather than 'xfs' consistently.

 > If you can't unfreeze the root filesystem by running xfs-freeze -u
 > immediately afterwards then that's a filesystem bug, not a problem
 > with the userspace command.

It may also be a good idea to point out in the man page that you should be
extremely careful running this if you are not logged in interactively, 
even a
disconnected ssh session will prevent you running xfs_freeze -u to manually
unfreeze the root filesystem.
Thanks
Pat Emblen

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

             reply	other threads:[~2012-12-03 23:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 23:53 Pat Emblen [this message]
2012-12-04  2:15 ` Bug#694624: /usr/sbin/xfs_freeze: freezes under lying (root) Dave Chinner
  -- strict thread matches above, loose matches on Subject: below --
2012-12-02 23:31 Pat Emblen
2012-12-03 21:48 ` Dave Chinner

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=50BD3B94.4070505@talbragar.com.au \
    --to=support@talbragar.com.au \
    --cc=694624@bugs.debian.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