public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Brian Foster <bfoster@redhat.com>, Eric Sandeen <sandeen@redhat.com>
Cc: Zorro Lang <zlang@redhat.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfs_copy: simplify first_agbno calculation
Date: Tue, 11 Nov 2014 10:01:55 -0600	[thread overview]
Message-ID: <546232F3.6030609@sandeen.net> (raw)
In-Reply-To: <20141111133705.GA38867@bfoster.bfoster>

On 11/11/14 7:37 AM, Brian Foster wrote:
> On Mon, Nov 10, 2014 at 04:15:35PM -0600, Eric Sandeen wrote:
>> After ffe9a9a xfsprogs: xfs_copy: fix data corruption of target,
>> xfs_copy started hitting an ASSERT for a 4k sector / 4k blocksize
>> filesystem:
>>
>> # dd if=/dev/zero of=test.img bs=1M count=1024
>> # mkfs.xfs -s size=4096 test.img
>> # xfs_copy test.img xfs.img
>> xfs_copy: xfs_copy.c:720: main: Assertion `((((((xfs_daddr_t)(3 << (mp)->m_sectbb_log)) + 1) * (1<<9)) + first_residue) % source_blocksize) == 0' failed.
>> Aborted
>>
>> I started digging through all the calculations below, and realized
>> that in the end, all it wants is the first filesystem block after
>> the AG header.  XFS_AGFL_BLOCK(mp) + 1 suffices for this purpose;
>> rip out the rest which seems overly complex and apparently bug-prone.
>>
>> I tested this by creating a 4g filesystem with combinations of
>> sector & block size between 512 and 4k, copying in /lib/modules,
>> running an xfs_copy of that, and running repair against the copy;
>> it all looks good.  It took a long time, but I will create a
>> simpler/shorter xfstest based on this.
>>
>> Reported-by: Zorro Lang <zlang@redhat.com>
>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>> ---
> 
> Looks Ok to me:
> 
> Reviewed-by: Brian Foster <bfoster@redhat.com>
> 
> I just noticed the bug... so the problem was basically the assumption
> that sector size == BBSIZE?

To be honest, I never quite figured out what the root cause bug
was; bad me.  The previous commit was supposed to *fix* the assumption
that sector size == BBSIZE.  But I got lost in all the gyrations.

I guess maybe I should work that out, but I'm not sure it's worth
it.  ;)

-Eric

> Brian
> 
>>
>> diff --git a/copy/xfs_copy.c b/copy/xfs_copy.c
>> index 7ce5ec9..279527c 100644
>> --- a/copy/xfs_copy.c
>> +++ b/copy/xfs_copy.c
>> @@ -475,7 +475,7 @@ main(int argc, char **argv)
>>  	int		open_flags;
>>  	xfs_off_t	pos, end_pos;
>>  	size_t		length;
>> -	int		c, first_residue, tmp_residue;
>> +	int		c;
>>  	__uint64_t	size, sizeb;
>>  	__uint64_t	numblocks = 0;
>>  	int		wblocks = 0;
>> @@ -697,27 +697,13 @@ main(int argc, char **argv)
>>  	ASSERT(source_blocksize % source_sectorsize == 0);
>>  	ASSERT(source_sectorsize % BBSIZE == 0);
>>  
>> -	if (source_blocksize > source_sectorsize)  {
>> -		/* get number of leftover sectors in last block of ag header */
>> -
>> -		tmp_residue = ((XFS_AGFL_DADDR(mp) + 1) * BBSIZE)
>> -					% source_blocksize;
>> -		first_residue = (tmp_residue == 0) ? 0 :
>> -			source_blocksize - tmp_residue;
>> -		ASSERT(first_residue % source_sectorsize == 0);
>> -	} else if (source_blocksize == source_sectorsize)  {
>> -		first_residue = 0;
>> -	} else  {
>> +	if (source_blocksize < source_sectorsize)  {
>>  		do_log(_("Error:  filesystem block size is smaller than the"
>>  			" disk sectorsize.\nAborting XFS copy now.\n"));
>>  		exit(1);
>>  	}
>>  
>> -	first_agbno = (((XFS_AGFL_DADDR(mp) + 1) * BBSIZE)
>> -				+ first_residue) / source_blocksize;
>> -	ASSERT(first_agbno != 0);
>> -	ASSERT(((((XFS_AGFL_DADDR(mp) + 1) * BBSIZE)
>> -				+ first_residue) % source_blocksize) == 0);
>> +	first_agbno = XFS_AGFL_BLOCK(mp) + 1;
>>  
>>  	/* now open targets */
>>  
>>
>> _______________________________________________
>> xfs mailing list
>> xfs@oss.sgi.com
>> http://oss.sgi.com/mailman/listinfo/xfs
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

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

      reply	other threads:[~2014-11-11 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 22:15 [PATCH] xfs_copy: simplify first_agbno calculation Eric Sandeen
2014-11-11  0:37 ` [PATCH] xfs_copy: fix ASSERT failure on 4k devices Eric Sandeen
2014-11-11 13:37 ` [PATCH] xfs_copy: simplify first_agbno calculation Brian Foster
2014-11-11 16:01   ` Eric Sandeen [this message]

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=546232F3.6030609@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=bfoster@redhat.com \
    --cc=sandeen@redhat.com \
    --cc=xfs@oss.sgi.com \
    --cc=zlang@redhat.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