Message-ID: <3C57F97A.7000400@sgi.com>
Date: Wed, 30 Jan 2002 07:47:38 -0600
From: Stephen Lord <lord@sgi.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011226
MIME-Version: 1.0
To: Chris Pascoe <c.pascoe@itee.uq.edu.au>
CC: linux-xfs@oss.sgi.com
Subject: Re: How long should an xfs_freeze take?
References: <023501c1a953$f059a0f0$47426682@csee.uq.edu.au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk
Status: O
Content-Length: 835
Lines: 33

Chris Pascoe wrote:

>Hi,
>
>I'm guessing an xfs_freeze shouldn't take this long, am I correct?
>
># time xfs_freeze -f /tst1
>
>real    344m40.434s
>user    0m0.000s
>sys     340m40.810s
>
>The system is a Dual CPU P3 Xeon with 1GB RAM (highmem enabled), running
>2.4.17 CVS, taken on 2002/01/23 (just before the -funsigned-char changes
>went through), with LVM 1.0.2 added (I see the same behaviour with 1.0.1,
>though).
>
How long freeze takes depends on how much data is dirty in the 
filesystem, it
should take a similar time to an unmount. However, unless this was a 
very large
and dirty filesystem this feels like a long time - although it was all 
system time,
so something was going on.

The spot you kept seeing on the stack does not make much sense, vn_count is
basically an atomic_read.

How repeatable is this? 

Steve