From: Eric Sandeen <sandeen@sandeen.net>
To: Tommy Wu <wu.tommy@gmail.com>, xfs <xfs@oss.sgi.com>
Subject: Re: xfsdump not work in 3.17
Date: Wed, 15 Oct 2014 22:33:46 -0500 [thread overview]
Message-ID: <543F3C9A.4060603@sandeen.net> (raw)
In-Reply-To: <CAGdb-8dvNOdBfZ3K_g_o22vN30yBJN+pwr-0sORC+Aubv5=9Cg@mail.gmail.com>
On 10/15/14 9:31 PM, Tommy Wu wrote:
> Hi!
>
> xfsdump 3.1.4
> xfsprogs 3.2.1
> linux kerenl 3.17/3.17.1
>
...
> It just create a small dump file, and if I run the same xfsdump again (or umount the filesystem), it will hang, like:
>
> fw1:/vol/backup/fw1# /sbin/xfsdump -v trace,drive=debug,media=debug -l 0 -o -J -F - /dev/vg/root | gzip > test.gz
> /sbin/xfsdump: using file dump (drive_simple) strategy
> /sbin/xfsdump: version 3.1.4 (dump format 3.0)
> /sbin/xfsdump: level 0 dump of fw1.teatime.com.tw:/
> /sbin/xfsdump: dump date: Thu Oct 16 10:30:09 2014
> /sbin/xfsdump: session id: b8354300-d54c-4131-b39c-7c0b63968208
> /sbin/xfsdump: session label: ""
> /sbin/xfsdump: ino map phase 1: constructing initial dump list
>
>
> switch back to kernel 3.16, the same command work fine.
>
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/xfs?id=a8b1ee8bafc765ebf029d03c5479a69aebff9693
addresses the small backup file, and
[PATCH] xfs: bulkstat doesn't release AGI buffer on error
(on the list) most likely addresses the hang, I think.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-16 3:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 2:31 xfsdump not work in 3.17 Tommy Wu
2014-10-16 3:33 ` Eric Sandeen [this message]
2014-10-16 4:14 ` Tommy Wu
2014-10-16 5:22 ` Eric Sandeen
2014-10-16 6:04 ` Tommy Wu
2014-10-24 1:43 ` Tommy Wu
2014-10-22 14:16 ` Michael L. Semon
2014-10-25 7:05 ` Michael L. Semon
2014-10-27 3:02 ` Michael L. Semon
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=543F3C9A.4060603@sandeen.net \
--to=sandeen@sandeen.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.