From: Mario Bachmann <mbachman@stud.uni-frankfurt.de>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfsdump-3.0.4 problems
Date: Tue, 17 Aug 2010 08:32:27 +0200 [thread overview]
Message-ID: <20100817083227.06e23889@x2.grafnetz> (raw)
In-Reply-To: <20100816223021.GL10429@dastard>
Am Tue, 17 Aug 2010 08:30:21 +1000
schrieb Dave Chinner <david@fromorbit.com>:
> On Mon, Aug 16, 2010 at 06:22:36PM +0200, Mario Bachmann wrote:
> > 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: WARNING: could not stat dirent .crack-attack ino 100663674: Das Argument ist ungültig: using null generation count in directory entry
>
> bulkstat is failing, indicating an invalid option was passed.
>
> > 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: Dump Status: SUCCESS
> >
> > And the file is 4,8 GB. All seems to be correct!
>
> I can't see any changes between 3.0.1 and 3.0.4 that would explain
> this. Did you run them on the same machine and kernel? Did you build
> them with the same compiler? If everything is the same, then perhaps
> you could bisect (only a few changes so should be quick) to point
> out the offending change.
>
> Cheers,
>
> Dave.
After some testing, I think it is NOT a problem with xfsdump, but with the new kernel 2.6.35.2. First I must correct my last posting: xfsdump-3.0.1 DO have the same problem as xfsdump-3.0.4 on kernel 2.6.35.2. It was just a coincidence that is worked one time without problems...
Machines: I have two x86_64 and one x86. All machines have the same problems after I upgraded all three Kernels from 2.6.34.x to 2.6.35.2. So I believe, it is a problem with 2.6.35.2 or the combination of [2.6.35.2 & xfsdump]
Compiler: I use "gcc (Gentoo 4.4.4-r1 p1.0, pie-0.4.5) 4.4.4".
Testing List (on one machine only):
works: x86_64, 2.6.34.4, xfsdump-3.0.1
works: x86_64, 2.6.34.4, xfsdump-3.0.4
failure: x86_64, 2.6.35.2, xfsdump-3.0.1 (worked only one time)
failure: x86_64, 2.6.35.2, xfsdump-3.0.4
Mario
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-17 6:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 16:22 xfsdump-3.0.4 problems Mario Bachmann
2010-08-16 22:30 ` Dave Chinner
2010-08-17 6:32 ` Mario Bachmann [this message]
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=20100817083227.06e23889@x2.grafnetz \
--to=mbachman@stud.uni-frankfurt.de \
--cc=david@fromorbit.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