public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
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 08:48:33 +1100	[thread overview]
Message-ID: <20121203214833.GB32450@dastard> (raw)
In-Reply-To: <50BBE4BC.3060708@talbragar.com.au>

On Mon, Dec 03, 2012 at 10:31:08AM +1100, Pat Emblen wrote:
> Well it's your call, but I'll make my case for changing it.
> - I think it is very dangerous default behaviour, particularly in
> scripts as it can prevent
> the possibility of logging in to unfreeze a frozen root.

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

> - The docs all strongly imply that it operates on mountpoints, so
> surely not many people
> would have diliberately used it on general paths?"

I use it that way all the time. I didn't even realise the man page
says "mount points only".....

>         xfs_freeze -f | -u mount-point"
> "The mount-point argument is the pathname of  the  directory  where  the
>        file system  is  mounted."
> - Because of the name and the wording of the man page, you don't
> expect xfs_freeze to
> freeze an ext4 file system that isn't even mounted on the path you
> pass to it?!

Yes, I do expect it to freeze the filesystem under the directory
that is passed, regardless of whether it is a mount point or not.
The man page is wrong.

For example, when you have a directory tree quota set up and
exported by NFS, the users will only know the export path of the
root of the directory tree, and they expect that to behave as if
that is a filesystem mounted at that point. Hence we have to be able
to support freeze being issued at such locations, not just the root
of the filesystem.

FWIW, fsfreeze says exactly the same thing in the man page, but
behaves identically to xfs_freeze...

> - It's logical to have it work on mountpoints only. You wouldn't
> expect umount or fdisk to
> work the same way? Do any other partition level tools work this way?

No, but filesystem utilities are not partition level tools and
expecting them to work the same way is incorrect.

> - At the very least I would expect it to require a 'force' option if
> it was going to freeze
> the root system.

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.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2012-12-03 21:48 UTC|newest]

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