From: Pat Emblen <talcom@talbragar.com.au>
To: 694624@bugs.debian.org
Subject: Bug#694624: PATCH freezes under lying (root)
Date: Sat, 08 Dec 2012 01:24:48 +1100 [thread overview]
Message-ID: <50C1FC30.5000708@talbragar.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 171 bytes --]
Hi, here's version 2.
I read the kernel patch info , but I'm mostly running off
http://www.debian.org/doc/manuals/maint-guide/modify.en.html
Thanks for your help.
Pat
[-- Attachment #2: update-man-xfs_freeze.patch --]
[-- Type: text/x-patch, Size: 2616 bytes --]
Description: Updates to the man page to more accurately describe the
behaviour of the program.
Forwarded: not-needed
Bug-Debian: http://bugs.debian.org/694624
Author: Patrick Emblen <support@talbragar.com.au>
--- a/man/man8/xfs_freeze.8
+++ b/man/man8/xfs_freeze.8
@@ -1,16 +1,16 @@
.TH xfs_freeze 8
.SH NAME
-xfs_freeze \- suspend access to an XFS filesystem
+xfs_freeze \- suspend access to a freezable filesystem
.SH SYNOPSIS
.B xfs_freeze \-f
|
.B \-u
-.I mount-point
+.I path
.fi
.SH DESCRIPTION
.B xfs_freeze
-suspends and resumes access to an XFS filesystem (see
-.BR xfs (5)).
+suspends and resumes access to compatible filesystems.
+The root filesystem is not treated in any special way and may also be frozen.
.PP
.B xfs_freeze
halts new access to the filesystem and creates a stable image on disk.
@@ -19,15 +19,12 @@
that support the creation of snapshots.
.PP
The
-.I mount-point
-argument is the pathname of the directory where the filesystem
-is mounted.
-The filesystem must be mounted to be frozen (see
-.BR mount (8)).
+.I path
+argument is the path to any directory within the mounted filesystem.
.PP
The
.B \-f
-flag requests the specified XFS filesystem to be
+flag requests the specified filesystem to be
frozen from new modifications.
When this is selected, all ongoing transactions in the filesystem
are allowed to complete, new write system calls are halted, other
@@ -55,16 +52,26 @@
must be supplied to
.BR xfs_freeze .
.SH NOTES
-A copy of a frozen XFS filesystem will usually have the same universally
+The command was originally specific to the XFS filesystem (see
+.BR
+xfs (5))but since Linux kernel version 2.6.29, the interface which
+XFS uses to freeze and unfreeze has been elevated to the VFS, so that
+this tool can now be used on many other Linux filesystems.
+.PP
+.BR xfs_freeze
+treats the root filesystem the same as any other filesystem.
+.B
+Take great care to verify that the path you specify contains the filesystem
+.B
+you intend to freeze and is not for example, an empty mount-point.
+It is usually impossible to logon to a system with a frozen root.
+.PP
+A copy of a frozen filesystem will usually have the same universally
unique identifier (UUID) as the original, and thus may be prevented from
being mounted.
-The XFS
+For XFS filesystems, the
.B nouuid
mount option can be used to circumvent this issue.
-.PP
-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.
.SH SEE ALSO
.BR xfs (5),
.BR lvm (8),
[-- Attachment #3: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2012-12-07 14:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50C1FC30.5000708@talbragar.com.au \
--to=talcom@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