Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g0VNAuP12153 for linux-xfs-outgoing; Thu, 31 Jan 2002 15:10:56 -0800 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g0VNAld12131 for ; Thu, 31 Jan 2002 15:10:48 -0800 Received: from zeus-e8.americas.sgi.com (zeus-e8.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id XAA193416 for ; Thu, 31 Jan 2002 23:10:49 +0100 (CET) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy-e185.americas.sgi.com [128.162.185.214]) by zeus-e8.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id QAA29255; Thu, 31 Jan 2002 16:09:26 -0600 (CST) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA22274; Thu, 31 Jan 2002 16:09:26 -0600 (CST) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id g0VM77911103; Thu, 31 Jan 2002 16:07:07 -0600 Subject: Re: How long should an xfs_freeze take? From: Steve Lord To: Chris Pascoe Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 31 Jan 2002 16:07:07 -0600 Message-Id: <1012514827.26397.257.camel@jen.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Status: O Content-Length: 2098 Lines: 61 On Thu, 2002-01-31 at 16:04, Chris Pascoe wrote: > Hi Steve, > > > > How repeatable is this? > > > > > > The problem was persistent across reboots - I rebooted to install a > > > different LVM version at some stage (move to 1.0.2, from 1.0.1), and it > > > occurred five times in a row after that. I just rebooted now to say > that it > > > still happens - but, alas - it doesn't want to any more. I'll try again > at > > > some random times throughout the day. > > I can repeat this fairly reliably now - do a meaningless rsync across the > disk (i.e. rsync itself to itself - makes it stat every file on the disk, I > guess), then try an xfs_freeze after the rsync completes: > > rsync -aH /tst1/ /tst1/ > time xfs_freeze -f /tst1 > > It's been hung there for ~10 minutes now, I've repeated this twice.... > rebooting - will try again... This time it doesn't want to do it.. :( > > This time I've done a rsync with real data: > > testbox# time rsync -e ssh -avH --stats root@fs:/home/01/ /tst1/ ; time xfs_freeze -f /tst1 ; time xfs_freeze -u /tst1 > > Number of files: 602545 > Number of files transferred: 292 > Total file size: 62690390294 bytes > Total transferred file size: 1728372390 bytes > Literal data: 177119547 bytes > Matched data: 1551577350 bytes > File list size: 15575582 > Total bytes written: 4690480 > Total bytes read: 195767044 > > wrote 4690480 bytes read 195767044 bytes 100808.41 bytes/sec > total size is 62690390294 speedup is 312.74 > > real 33m7.243s > user 1m34.200s > sys 2m8.250s > > I'm sitting waiting for the xfs_freeze again - so I can replicate > the problem, yes. It takes at least 40 minutes to complete xfs_freeze's > after this point (i.e. you can go xfs_freeze -f ; xfs_freeze -u ; > xfs_freeze -f ; xfs_freeze -u, and the second freeze still takes > forever!), during which time the machine is completely unresponsive. > > Chris We are looking - or at least Eric is.... Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com