xfs
[Top] [All Lists]

Re: xfsdump INTERRUPT issue

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: xfsdump INTERRUPT issue
From: Jeffrey Ellis <jellis@xxxxxxxx>
Date: Wed, 19 Dec 2012 17:12:12 -0500
Cc: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <20121219220010.GM15182@dastard>
References: <CCF65180.B0AE2%jellis@xxxxxxxx> <CCF7512F.B0B5A%jellis@xxxxxxxx> <20121219220010.GM15182@dastard>
Dave, is there a way of piping dmesg to a file?

Best,
J. 

On Dec 19, 2012, at 5:00 PM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:

> 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>