Date: Fri, 9 Apr 2004 10:51:48 -0500 (CDT)
From: Eric Sandeen <sandeen@sgi.com>
To: Stefan Smietanowski <stesmi@stesmi.com>
cc: "IKARASHI, Seiichi" <ikarashi@miraclelinux.com>,
        Chris Wedgwood <cw@f00f.org>, Steve Lord <lord@xfs.org>,
        Christoph Hellwig <hch@infradead.org>, <linux-xfs@oss.sgi.com>
Subject: Re: synchronization of XFS
In-Reply-To: <4075FACC.3010105@stesmi.com>
Message-ID: <Pine.LNX.4.44.0404091049360.15480-100000@stout.americas.sgi.com>
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
Precedence: bulk
Content-Length: 1076
Lines: 34

On Fri, 9 Apr 2004, Stefan Smietanowski wrote:

> > import fsset
> > if fsset.isValidXFS(bootDev):
> >     // execute xfs_freeze -f for bootDev
> >     // execute xfs_freeze -u for bootDev
> 
> Excellent. I take it "if fsset.isValidXFS(bootDev)" is code and not
> pseudo-code. 

Correct - that reads the first few bytes and looks for 
the xfs magic number.

> I'll have to try that. I know the "execute xfs_freeze..."
> is pseudo-code.
> 
> Hmmm. Wait, I just thought of something actually.
> 
> Regardless of if I have that if there or not I only need to do
> xfs_freese -[fu] /boot actually since it just dawned on me what Chris W
> said. Doing xfs_freeze -f /boot will freeze the partition where /boot
> is located if /boot is a dir on /.

Yep, was going to suggest that.

> I'll try that if you wrote there and get back to you tomorrow.
> Right now it's pretty late .. 0320. ouch... Yup, definately tomorrow.

Great, thanks for doing all the work on this.  Perhaps when you
get it tidied up you can add this info to the Red Hat bugzilla
bug tracking this problem?

-Eric