From: Dave Chinner <david@fromorbit.com>
To: Pat Emblen <support@talbragar.com.au>, 694624@bugs.debian.org
Subject: Bug#694624: /usr/sbin/xfs_freeze: freezes under lying (root)
Date: Tue, 4 Dec 2012 13:15:11 +1100 [thread overview]
Message-ID: <20121204021511.GC32450@dastard> (raw)
In-Reply-To: <50BD3B94.4070505@talbragar.com.au>
On Tue, Dec 04, 2012 at 10:53:56AM +1100, Pat Emblen wrote:
> > 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,
Patches to fix the documentation are welcome...
> and perhaps use
> 'filesystem' rather than 'xfs' consistently.
>From the man page:
In Linux kernel version 2.6.29, the interface which XFS
uses to freeze and unfreeze was elevated to the VFS, so that
this tool can now be used on many other Linux filesystems.
> > 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.
Sure. Patches are welcome. ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-12-04 2:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 23:53 Bug#694624: /usr/sbin/xfs_freeze: freezes under lying (root) Pat Emblen
2012-12-04 2:15 ` Dave Chinner [this message]
-- 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=20121204021511.GC32450@dastard \
--to=david@fromorbit.com \
--cc=694624@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