xfs
[Top] [All Lists]

Re: xfsdump INTERRUPT issue

To: "J. Ellis" <jellis@xxxxxxxx>
Subject: Re: xfsdump INTERRUPT issue
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 20 Dec 2012 09:00:10 +1100
Cc: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <CCF7512F.B0B5A%jellis@xxxxxxxx>
References: <CCF65180.B0AE2%jellis@xxxxxxxx> <CCF7512F.B0B5A%jellis@xxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Wed, Dec 19, 2012 at 11:10:39AM -0500, J. Ellis wrote:
> Ok, here's the output of iostat, /proc/meminfo, and finally the report from
> xfsrestore when interrupted.
> 
> Best,
> J.
> 
> 
> iostat -d -x -m 5

So there's a tiny amount of IO going to /dev/sdc - 1 or 2 IOs per
second. Not much.

> /proc/meminfo
> 
> MemTotal:        6184324 kB
> MemFree:         4675040 kB

And you haven't run out of memory...

> ^Cxfsrestore: SIGINT received
> 
>  ========================= status and control dialog
> ==========================
> 
> status at 10:52:05: 45/120310 files restored, 0.0% complete, 2049 seconds
> elapsed

Oh, and it's xfsrestore that is hanging.

> This was the same number of files restored reported when the process began.

So it's having problems when writing files to the realtime device.
When it is like this, can you post the output of dmesg after doing
this:

# echo w > /proc/sysrq-trigger
# echo l > /proc/sysrq-trigger
# dmesg

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>