[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <FDC91B229D965C458E3615E98C48ADDD0EC41F40@dggemm511-mbx.china.huawei.com>
Date: Tue, 3 Jul 2018 11:15:21 +0000
From: "Gaoming (ming, consumer BG)" <gaoming20@...wei.com>
To: "Theodore Y. Ts'o" <tytso@....edu>
CC: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Liqingchao (sorp)" <sorp.liqingchao@...wei.com>,
"Shenchen (harry)" <harry.shen@...wei.com>,
"miaoxie (A)" <miaoxie@...wei.com>,
"yangfei (D)" <yangfei39@...wei.com>,
"Renlipeng (OS driver)" <renlipeng@...wei.com>
Subject: 答复: 答复: 答复: 答复: 答复: 答复: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not integer,incompatible for ancient android devices
-----邮件原件-----
发件人: Theodore Y. Ts'o [mailto:tytso@....edu]
发送时间: 2018年7月3日 18:36
收件人: Gaoming (ming, consumer BG)
抄送: linux-ext4@...r.kernel.org; linux-kernel@...r.kernel.org; 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
Powered by blists - more mailing lists