public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Ngo, Andrew" <andrew.ngo@lmco.com>
Cc: v9fs-developer@lists.sourceforge.net, xfs@oss.sgi.com, "Johnson,
	Je" <je.johnson@lmco.com>
Subject: Re: Stale XFS mount for Kernel 2.6.25.14
Date: Tue, 14 Oct 2008 13:15:34 +1100	[thread overview]
Message-ID: <20081014021534.GI10716@disturbed> (raw)
In-Reply-To: <8604545CB7815D419F5FF108D3E434BA3BD62F@emss04m05.us.lmco.com>

[Andrew, Please don't top post replies - it makes it
completely impossible to folow the thread. ]

> -----Original Message-----
On Mon, Oct 13, 2008 at 10:04:27PM -0400, Ngo, Andrew wrote:
On Mon, Oct 13, 2008 at 10:04:27PM -0400, Ngo, Andrew wrote:
> 
> Dave,
> 
> Do you know of a solution to this problem?  Currently this is a major
> impact for my system.  Thanks in advance.

I don't know what the problem is, so I certainly don't have
a solution for you. You'll need to provide a whole lot more detail
about your system and problem for us to make any sense of it.
Such as:

What hardware do you have (including storage)?

What's the storage structure (DM, MD, iSCSI, etc)?

Output of 'xfs_info <mtpt>'?

What are you really trying to acheive with the remount command?

Is the filesystem busy at the time the ro,remount is run?
(e.g. any large background writes occurring?)

Does the problem go away if you do:

# xfs_freeze -f <mtpt>
# xfs_freeze -u <mtpt>
# mount -o ro,remount <mtpt>

Or does the first freeze command trigger the same problem?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2008-10-14  2:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13  2:10 Stale XFS mount for Kernel 2.6.25.14 Ngo, Andrew
2008-10-13  3:59 ` Dave Chinner
2008-10-13 12:06   ` Ngo, Andrew
2008-10-14  2:04     ` Ngo, Andrew
2008-10-14  2:15       ` Dave Chinner [this message]
2008-10-14  3:40         ` Ngo, Andrew
2008-10-14  5:53           ` Dave Chinner
2008-10-14 21:54             ` Ngo, Andrew
     [not found] <8604545CB7815D419F5FF108D3E434BA017C6427@emss04m05.us.lmco.com>
     [not found] ` <20081020230802.GA18495@disturbed>
2008-11-03 20:49   ` Ngo, Andrew
2008-11-04  6:05     ` Dave Chinner
2009-01-14 23:50       ` Ngo, Andrew
2009-01-15  8:50         ` 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=20081014021534.GI10716@disturbed \
    --to=david@fromorbit.com \
    --cc=andrew.ngo@lmco.com \
    --cc=je.johnson@lmco.com \
    --cc=v9fs-developer@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox