[lkml]   [2018]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject答复: 答复: 答复: 答复: 答复: 答复: 答复: [PA TCH] ext4: e2fsprogs: fix inode bitmap num no t integer,incompatible for ancient android de vices

发件人: Theodore Y. Ts'o []
发送时间: 2018年7月3日 18:36
收件人: Gaoming (ming, consumer BG)
抄送:;; 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

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
 \ /
  Last update: 2018-07-03 13:16    [W:0.099 / U:1.280 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site