All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Ni <xni@redhat.com>
To: Guoqing Jiang <gqjiang@suse.com>
Cc: linux-raid@vger.kernel.org, ncroxon@redhat.com,
	jes sorensen <jes.sorensen@gmail.com>
Subject: Re: [MDADM PATCH 1/1] Array size is wrong when run mdadm -E
Date: Tue, 4 Jul 2017 22:40:31 -0400 (EDT)	[thread overview]
Message-ID: <961848702.28655534.1499222431603.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <03fe6bb9-714e-bebb-1bbe-63a9d6ccee69@suse.com>



----- Original Message -----
> From: "Guoqing Jiang" <gqjiang@suse.com>
> To: "Xiao Ni" <xni@redhat.com>
> Cc: linux-raid@vger.kernel.org, ncroxon@redhat.com, "jes sorensen" <jes.sorensen@gmail.com>
> Sent: Wednesday, July 5, 2017 9:56:35 AM
> Subject: Re: [MDADM PATCH 1/1] Array size is wrong when run mdadm -E
> 
> 
> 
> On 07/04/2017 05:55 PM, Xiao Ni wrote:
> >
> > ----- Original Message -----
> >> From: "Guoqing Jiang" <gqjiang@suse.com>
> >> To: "Xiao Ni" <xni@redhat.com>, linux-raid@vger.kernel.org
> >> Cc: ncroxon@redhat.com, "jes sorensen" <jes.sorensen@gmail.com>
> >> Sent: Tuesday, July 4, 2017 5:03:30 PM
> >> Subject: Re: [MDADM PATCH 1/1] Array size is wrong when run mdadm -E
> >>
> >>
> >>
> >> On 07/04/2017 02:50 PM, Xiao Ni wrote:
> >>> The size of array shows wrongly. It shifs wrong number.
> >>>
> >>> Signed-off-by: Xiao Ni <xni@redhat.com>
> >>> ---
> >>>    super1.c | 2 +-
> >>>    1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/super1.c b/super1.c
> >>> index 86ec850..f3b864d 100644
> >>> --- a/super1.c
> >>> +++ b/super1.c
> >>> @@ -366,7 +366,7 @@ static void examine_super1(struct supertype *st, char
> >>> *homehost)
> >>>    		}
> >>>    		if (ddsks) {
> >>>    			long long asize = __le64_to_cpu(sb->size);
> >>> -			asize = (asize << 9) * ddsks / ddsks_denom;
> >>> +			asize = (asize << 10) * ddsks / ddsks_denom;
> >>>    			printf("     Array Size : %llu%s\n",
> >>>    			       asize >> 10,  human_size(asize));
> >>>    		}
> >> IIRC, sb->size represents the num of sectors, so the shift should be 9.
> > Yes, it should be 9. It should pass bytes to human_size. Thanks for this.
> > It was introduced in d4633e06dfc01723911627fcb104af2ffb6f6a95. So there is
> > the same problem in super0. Is it ok:
> >
> > diff --git a/super0.c b/super0.c
> > index 756cab5..4b4680c 100644
> > --- a/super0.c
> > +++ b/super0.c
> > @@ -131,9 +131,9 @@ static void examine_super0(struct supertype *st, char
> > *homehost)
> >                  }
> >                  if (ddsks) {
> >                          long long asize = sb->size;
> > -                       asize = (asize << 10) * ddsks / ddsks_denom;
> > +                       asize = (asize << 9) * ddsks / ddsks_denom;
> >                          printf("     Array Size : %llu%s\n",
> > -                              asize >> 10,  human_size(asize));
> > +                              asize >> 9,  human_size(asize));
> >                  }
> 
> No, for 0.9 metadata, sb->size means KB not sector.
> 
Thanks for this.

> >          }
> >          printf("   Raid Devices : %d\n", sb->raid_disks);
> > diff --git a/super1.c b/super1.c
> > index 86ec850..2bb1454 100644
> > --- a/super1.c
> > +++ b/super1.c
> > @@ -368,7 +368,7 @@ static void examine_super1(struct supertype *st, char
> > *homehost)
> >                          long long asize = __le64_to_cpu(sb->size);
> >                          asize = (asize << 9) * ddsks / ddsks_denom;
> >                          printf("     Array Size : %llu%s\n",
> > -                              asize >> 10,  human_size(asize));
> > +                              asize >> 9,  human_size(asize));
> >                  }
> >                  if (sb->size != sb->data_size)
> >                          printf("  Used Dev Size : %llu%s\n",
> 
> It is better that you can provide the output of "mdadm -E DISK" etc to prove
> current code is wrong, at least I can see correct output from my side.

[root@dell-per210-01 mdadm]# mdadm -E /dev/loop0 
/dev/loop0:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 34f18365:ebf46416:ae1f365d:71cc579c
           Name : 0
  Creation Time : Tue Jul  4 02:09:03 2017
     Raid Level : raid5
   Raid Devices : 3

 Avail Dev Size : 8261632 (3.94 GiB 4.23 GB)
     Array Size : 6291456 (6.00 GiB 6.44 GB)
  Used Dev Size : 6291456 (3.00 GiB 3.22 GB)

Ah, I know it wants to show Array Size in KB. It's a raid5 with 3 loop devices. 
I thought they are all sectors subconsciously. But it's better to show sizes with 
the same unit. Right?

Regards
Xiao



  reply	other threads:[~2017-07-05  2:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04  6:50 [MDADM PATCH 1/1] Array size is wrong when run mdadm -E Xiao Ni
2017-07-04  9:03 ` Guoqing Jiang
2017-07-04  9:55   ` Xiao Ni
2017-07-05  1:56     ` Guoqing Jiang
2017-07-05  2:40       ` Xiao Ni [this message]
2017-07-05  3:21         ` Guoqing Jiang
2017-07-05  3:24           ` Xiao Ni

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=961848702.28655534.1499222431603.JavaMail.zimbra@redhat.com \
    --to=xni@redhat.com \
    --cc=gqjiang@suse.com \
    --cc=jes.sorensen@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=ncroxon@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 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.