答复: 答复: 答复: 答复: 答复: 答复: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not integer,incompatible for ancient android devices

[Gaoming (ming, consumer BG)]

-----邮件原件-----
发件人: Theodore Y. Ts'o [mailto:tytso@xxxxxxx] 
发送时间: 2018年7月3日 18:36
收件人: Gaoming (ming, consumer BG)
抄送: linux-ext4@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; Liqingchao (sorp); Shenchen (harry); miaoxie (A); yangfei (D); Renlipeng (OS driver)
主题: Re: 答复: 答复: 答复: 答复: 答复: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not integer,incompatible for ancient android devices

On Tue, Jul 03, 2018 at 12:58:48AM +0000, Gaoming (ming, consumer BG) wrote:
> And can you help me understand *why* such a choice was made?
> -----if there is such a problem in your devices, how will you do? Is there any other choice?
> ----- of course, you cannot format the partition.

You misunderstand my question.  Why was the choice of a blocksize of
1024 made?

-----some one choose, not me . I guess they want get more inodes in 20M filesystem.

I'm trying to understand how many devices, and why any other
manufacture would make, what seems to me, to be a completely insane
choice.

How long has Huawei been using a 1024 byte blocksize?  And why?  And
for how many devices?  Essentially, I'm trying to figure out if this
was a Huawei-specific mistake.
----- I cannot answer this question.

					- Ted