[Top] [All Lists]

Re: xfsrestore report SUCCESS but not restore all files in kernel 3.17

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: xfsrestore report SUCCESS but not restore all files in kernel 3.17
From: Tommy Wu <wu.tommy@xxxxxxxxx>
Date: Wed, 29 Oct 2014 17:21:52 +0800
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0hRSA4DhT1KWp3/RGfL/P5NpBCTKb7R8S+Yd6GhSJZs=; b=EhKNvBF693+R83NC+jb3O+SOKwlHqYIE8wYJ9w7PgqM8VbW725gUaUI/fDQaEBKt2o bJnwjtTqlDVhOA5cRORBGcCw2oXW3IUFeSlR2iPP46aF7eSqQ4eceWhC3iaRD/66xshS cBNeQs9DJSo8aEiFiH6MI+NEpzjcqegv0t6lQsd5w88wbJM36Js/OeeprsHfaSbCJwU6 j7++ZVZ+oP5Z78p45V7SqfDd54Y8A3o8LosB6js+f/dzIgevexfV/zujpm9m0QR916oJ gah/y58DaJMxCf4EyigVD3HHkPhwUogwbwSgTkRYiVhTA55bt/giayEN4IbUBmCIWKoX 02VA==
In-reply-to: <20141029075134.GB13323@dastard>
References: <CAGdb-8cnmCs=L0RPvE8+5jn3nmZoviiZtQBbo9S-BThA+3cBKg@xxxxxxxxxxxxxx> <5450686F.9070307@xxxxxxxxxxx> <CAGdb-8d5-GuB40ZgP6uM5aQMi+qqaeFd=xqzuxWhM+1AaoLSVw@xxxxxxxxxxxxxx> <54506CD9.90403@xxxxxxxxxxx> <CAGdb-8cGAzT_0ck-pJyQX-OcnE_3FPCA9TesHW7c_raDSKEXWg@xxxxxxxxxxxxxx> <20141029044017.GG16186@dastard> <CAGdb-8e=wttjj+wTj8wqRWyUUz+AUmz-O0=r3+HoJ5zGgV-dkQ@xxxxxxxxxxxxxx> <20141029075134.GB13323@dastard>
Same testing in same machine (just different kernel).

xfsdump will hang (the test.xfsdump.gz size stop around 57M)

3.17.1 (with 2 patches):
xfsdump generate the dump file, but xfsrestore can't restore all files from the dump file.
I think the dump is corrupted, can't restore it also in kernel 3.16.5.

everything work fine.

2014-10-29 15:51 GMT+08:00 Dave Chinner <david@xxxxxxxxxxxxx>:
On Wed, Oct 29, 2014 at 02:46:33PM +0800, Tommy Wu wrote:
> it will hang after this message (the kernel in above git repo):
> /sbin/xfsdump: dumping non-directory files
> console show the below message every 2 minutes:
> [Â 480.387308] INFO: task xfsdump:2717 blocked for more than 120 seconds.

I think there might be something else wrong with your system.

What's the stack trace associated with that? If there's none,
what's the output of 'echo w > /proc/sysrq-trigger' in dmesg?


Dave Chinner


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