All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: xfs_freeze same as umount?   How is that helpful?
Date: Thu, 04 Oct 2012 15:39:33 -0700	[thread overview]
Message-ID: <506E1025.8050605@tlinx.org> (raw)
In-Reply-To: <CAGpXXZJuWRAMnJfZKJMZ3N=0EwcfYOEwX+iteyk9hY7ojWA+XA@mail.gmail.com>

Greg Freemyer wrote:
> Conceptually it is typically:
> - quiesce system
----
	Um... it seems that this is equivalent to being
able to umount the disk?

When I tried xfs_freeze / fs_freeze got fs-busy -- same as I would
if I tried to umount it.

I thought the point of xfs_freeze was to allow it to be brought to
a consistent state without unmounting it?

Coincidentally, after trying a few freezes, the system froze.

Last message in log was 'fetchmail' (that might have been writing a
log to /home), had hung for 120 seconds...

That was all she wrote before the entire system 'froze'...


So shouldn't xfs_freeze work without having to to shut down every
process on it?  If not, then how is it different than umount?





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

  parent reply	other threads:[~2012-10-04 22:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 15:30 get filename->inode mappings in bulk for a live fs? Linda Walsh
2012-10-04 18:01 ` Greg Freemyer
2012-10-04 18:29   ` Linda Walsh
2012-10-04 18:59     ` Greg Freemyer
2012-10-04 22:39   ` Linda Walsh [this message]
2012-10-04 23:32     ` xfs_freeze same as umount? How is that helpful? Dave Chinner
2012-10-05  0:10       ` Linda Walsh
2012-10-05  0:36         ` Dave Chinner
2012-10-04 22:49 ` get filename->inode mappings in bulk for a live fs? 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=506E1025.8050605@tlinx.org \
    --to=xfs@tlinx.org \
    --cc=xfs@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.