From: Mario Bachmann <mbachman@stud.uni-frankfurt.de>
To: xfs@oss.sgi.com
Subject: xfsdump-3.0.4 problems
Date: Mon, 16 Aug 2010 18:22:36 +0200 [thread overview]
Message-ID: <20100816182236.249a2a0f@x2.grafnetz> (raw)
Hello,
my kernel is
Linux x2 2.6.35.2 #1 SMP Sun Aug 15 00:32:14 CEST 2010 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ AuthenticAMD GNU/Linux
I get a lot of Warnings with xfsdump-3.0.4 (booth, gentoo package 3.0.4-r1 and git-version):
x2 ~/source/d/xfsdump/dump # ./xfsdump -l0 -L "Test" - /dev/sda2 |gzip - > /mnt/data2/dump_text.gz
./xfsdump: using file dump (drive_simple) strategy
./xfsdump: version 3.0.4 (dump format 3.0) - Running single-threaded
./xfsdump: level 0 dump of x2:/home
./xfsdump: dump date: Mon Aug 16 17:34:30 2010
./xfsdump: session id: 288ed27c-2b26-4c8b-a5d4-bfd1a32f4b6f
./xfsdump: session label: "Test"
./xfsdump: ino map phase 1: constructing initial dump list
./xfsdump: ino map phase 2: skipping (no pruning necessary)
./xfsdump: ino map phase 3: skipping (only one dump stream)
./xfsdump: ino map construction complete
./xfsdump: estimated dump size: 3236335808 bytes
./xfsdump: creating dump session media file 0 (media 0, file 0)
./xfsdump: dumping ino map
./xfsdump: dumping directories
./xfsdump: WARNING: could not stat dirent .crack-attack ino 100663674: Das Argument ist ungültig: using null generation count in directory entry
./xfsdump: WARNING: could not stat dirent .kvirc4.rc ino 239: Das Argument ist ungültig: using null generation count in directory entry
./xfsdump: WARNING: could not stat dirent .recently-used ino 240: Das Argument ist ungültig: using null generation count in directory entry
./xfsdump: WARNING: could not stat dirent .DownloadManager ino 100663836: Das Argument ist ungültig: using null generation count in directory entry
./xfsdump: WARNING: could not stat dirent .distcc ino 33554725: Das Argument ist ungültig: using null generation count in directory entry
./xfsdump: WARNING: could not stat dirent .javafx_eula_accepted ino 1327: Das Argument ist ungültig: using null generation count in directory entry
./xfsdump: WARNING: could not stat dirent solar_kassel_thomas.txt ino 1671: Das Argument ist ungültig: using null generation count in directory entry
[thousands of these messages...]
./xfsdump: WARNING: could not stat dirent -07a9540007aa7500-0000000000 ino 38797391: Das Argument ist ungültig: using null generation count in directory entry
./xfsdump: dumping non-directory files
./xfsdump: ending media file
./xfsdump: media file size 3319179552 bytes
./xfsdump: dump size (non-dir files) : 3313078008 bytes
./xfsdump: dump complete: 174 seconds elapsed
./xfsdump: Dump Status: SUCCESS
At the end there is a file with 2,8 GB. When restored, I have 3,2 GB.
A lot of files simply are not there!
With the "old" version xfsdump-3.0.1, I get no warnings!
xfsdump -l0 -L "Test" - /dev/sda2 |gzip - > /mnt/data2/dump301_test.gz
xfsdump: using file dump (drive_simple) strategy
xfsdump: version 3.0.1 (dump format 3.0) - Running single-threaded
xfsdump: level 0 dump of x2:/home
xfsdump: dump date: Mon Aug 16 18:14:47 2010
xfsdump: session id: b75a088f-6481-4583-8020-7c67fbe92bca
xfsdump: session label: "Test"
xfsdump: ino map phase 1: constructing initial dump list
xfsdump: ino map phase 2: skipping (no pruning necessary)
xfsdump: ino map phase 3: skipping (only one dump stream)
xfsdump: ino map construction complete
xfsdump: estimated dump size: 6000020480 bytes
xfsdump: creating dump session media file 0 (media 0, file 0)
xfsdump: dumping ino map
xfsdump: dumping directories
xfsdump: dumping non-directory files
xfsdump: ending media file
xfsdump: media file size 5701306656 bytes
xfsdump: dump size (non-dir files) : 5691937016 bytes
xfsdump: dump complete: 308 seconds elapsed
xfsdump: Dump Status: SUCCESS
And the file is 4,8 GB. All seems to be correct!
Mario
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-08-16 16:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 16:22 Mario Bachmann [this message]
2010-08-16 22:30 ` xfsdump-3.0.4 problems Dave Chinner
2010-08-17 6:32 ` Mario Bachmann
2010-08-17 7:13 ` Dave Chinner
2010-08-17 7:53 ` Mario Bachmann
2010-08-17 9:05 ` Dave Chinner
2010-08-17 11:45 ` [PATCH] " Dave Chinner
2010-08-17 15:47 ` Mario Bachmann
2010-08-18 10:10 ` Christoph Hellwig
2010-08-27 11:18 ` Iustin Pop
2010-08-27 11:40 ` Dave Chinner
2010-09-24 9:53 ` Mario Bachmann
2010-10-03 6:20 ` Christoph Hellwig
2010-08-17 9:03 ` Christoph Hellwig
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=20100816182236.249a2a0f@x2.grafnetz \
--to=mbachman@stud.uni-frankfurt.de \
--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