public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Tommy Wu <wu.tommy@gmail.com>
Cc: xfs <xfs@oss.sgi.com>
Subject: Re: xfsrestore report SUCCESS but not restore all files in kernel 3.17
Date: Fri, 31 Oct 2014 15:25:11 +1100	[thread overview]
Message-ID: <20141031042511.GN13323@dastard> (raw)
In-Reply-To: <20141031034925.GM13323@dastard>

On Fri, Oct 31, 2014 at 02:49:25PM +1100, Dave Chinner wrote:
> On Fri, Oct 31, 2014 at 09:51:27AM +0800, Tommy Wu wrote:
> > After apply this patch, xfsdump will hang again.
> > 
> > the log for xfsdump:
> > https://mega.co.nz/#!tUgz3QrC!q7Ix53sl9lYCg0iKRHjgOqF0tZJAVKHBNz0OHWof-ds
> > 
> > But 'echo w > /proc/sysrq-trigger' no any blocked task in dmesg.
> 
> echo l > /proc/sysrq-trigger
> echo t > /proc/sysrq-trigger

Also, I just cannot reproduce a hung dump or a broken restore,
so can you take an unobfuscated metadump of the source filesystem
(i.e. the one you are running dump on) so I can try on an exact
image of the filesystem you are having troubles on?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-10-31  4:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29  4:06 xfsrestore report SUCCESS but not restore all files in kernel 3.17 Tommy Wu
2014-10-29  4:09 ` Eric Sandeen
2014-10-29  4:27   ` Tommy Wu
2014-10-29  4:28     ` Eric Sandeen
2014-10-29  4:30       ` Tommy Wu
2014-10-29  4:40         ` Dave Chinner
2014-10-29  6:46           ` Tommy Wu
2014-10-29  7:51             ` Dave Chinner
2014-10-29  9:03               ` Tommy Wu
2014-10-29  9:21               ` Tommy Wu
2014-10-29 10:33                 ` Dave Chinner
2014-10-29 10:43                   ` Dave Chinner
2014-10-29 12:32                     ` Tommy Wu
2014-10-29 19:50                       ` Dave Chinner
2014-10-29 20:52                         ` Dave Chinner
2014-10-29 21:25 ` Dave Chinner
     [not found]   ` <CAGdb-8dbGRu_GWB4qoeNP8Kso2hzkLcuFS9Pwtnm2xOkP2T0rQ@mail.gmail.com>
2014-10-30  5:03     ` Dave Chinner
2014-10-30  8:39       ` Tommy Wu
2014-10-30 10:39         ` Tommy Wu
2014-10-30 23:04         ` Dave Chinner
2014-10-31  0:09           ` Dave Chinner
2014-10-31  1:51             ` Tommy Wu
2014-10-31  3:49               ` Dave Chinner
2014-10-31  4:25                 ` Dave Chinner [this message]
2014-10-31  4:42                   ` Tommy Wu
2014-10-31  4:55                     ` Eric Sandeen
2014-10-31  5:40                   ` Tommy Wu
2014-11-07  1:05                     ` Tommy Wu
2014-11-07  4:37                       ` Dave Chinner
2014-10-31  4:40                 ` Tommy Wu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141031042511.GN13323@dastard \
    --to=david@fromorbit.com \
    --cc=wu.tommy@gmail.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox