From: Rich Johnston <rjohnston@sgi.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH V3] xfsrestore: fix fs uuid order check for incremental restores
Date: Fri, 11 Sep 2015 12:01:34 -0500 [thread overview]
Message-ID: <55F308EE.3010109@sgi.com> (raw)
In-Reply-To: <20150908124726.GA5305@bfoster.bfoster>
On 09/08/2015 07:47 AM, Brian Foster wrote:
> On Thu, Sep 03, 2015 at 06:43:46PM -0500, Rich Johnston wrote:
>> Restoring an incremental level 1 dump will fail with the following error
>> if the fs uuid of the most recent level 0 dump in the inventory does not
>> match level 1 dump we are restoring.
...
>> Index: b/inventory/inv_api.c
>> ===================================================================
>> --- a/inventory/inv_api.c
>> +++ b/inventory/inv_api.c
>> @@ -596,69 +596,78 @@ inv_free_session(
...
>>
>> - return invmgr_query_all_sessions((void *) &level, /* in */
>> - (void **) ses, /* out */
>> - (search_callback_t) lastsess_level_lessthan);
>> + return invmgr_query_all_sessions(fsidp /* fs uuid */
>
> This doesn't compile because of a missing comma after fsidp above.
>
My mistake, happened while cleaning up whitespace.
...
>> Index: b/inventory/inv_mgr.c
>> ===================================================================
>> --- a/inventory/inv_mgr.c
>> +++ b/inventory/inv_mgr.c
...
>> @@ -178,26 +180,27 @@ invmgr_query_all_sessions (
>> "INV: Open failed on %s\n"),
>> fname
>> );
>> - return BOOL_FALSE;
>> + continue;
>> }
>> - result = search_invt( invfd, inarg, &objectfound, func );
>> + result = search_invt(fsidp, invfd, inarg, &objectfound, func);
>> close(invfd);
>>
>> /* if error return BOOL_FALSE */
>> if (result < 0) {
>> - return BOOL_FALSE;
>> + return ret;
>
> Should this always return false? It's now possible to return true if an
> error occurs after we've found one object.
*nod* Thanks I missed that one.
I'll have a V4 out shortly.
--Rich
>
> The rest seems Ok to me.
>
> Brian
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-09-11 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 16:27 [PATCH] xfsrestore: fix fs uuid order check for incremental restores Rich Johnston
2015-08-26 21:31 ` Dave Chinner
2015-08-26 22:53 ` Rich Johnston
2015-09-01 19:36 ` Rich Johnston
2015-09-02 13:21 ` [RESEND PATCH] " Brian Foster
2015-09-02 18:49 ` Rich Johnston
2015-09-03 14:07 ` [PATCH V2] " Rich Johnston
2015-09-03 14:23 ` Rich Johnston
2015-09-03 23:43 ` [PATCH V3] " Rich Johnston
2015-09-08 12:47 ` Brian Foster
2015-09-11 17:01 ` Rich Johnston [this message]
2015-09-11 17:14 ` [PATCH V4] " Rich Johnston
2015-09-11 19:22 ` Brian Foster
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=55F308EE.3010109@sgi.com \
--to=rjohnston@sgi.com \
--cc=bfoster@redhat.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