All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junling Zheng <zhengjunling@huawei.com>
To: Fan Li <fanofcode.li@samsung.com>,
	'Jaegeuk Kim' <jaegeuk@kernel.org>,
	heyunlei@huawei.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v2] f2fs-tools: set segment_count in super block correctly
Date: Thu, 4 Feb 2016 17:53:16 +0800	[thread overview]
Message-ID: <56B31F8C.8050800@huawei.com> (raw)
In-Reply-To: <001c01d15f2f$4caad220$e6007660$@samsung.com>

On 2016/2/4 17:33, Fan Li wrote:
> 
> 
>> -----Original Message-----
>> From: Junling Zheng [mailto:zhengjunling@huawei.com]
>> Sent: Thursday, February 04, 2016 10:52 AM
>> To: Fan Li; 'Jaegeuk Kim'; heyunlei@huawei.com
>> Cc: linux-f2fs-devel@lists.sourceforge.net
>> Subject: Re: [f2fs-dev] [PATCH v2] f2fs-tools: set segment_count in super block correctly
>>
>> On 2016/2/3 13:29, Fan Li wrote:
>>> Now f2fs will check statistics recorded in super block in
>>> sanity_check_area_boundary() during mount,if number of segments per
>>> section is greater than 1, and the disk space isn't aligned with
>>> section,
>>
>> Hi Fan, Hi Kim:
>>
>> I'm uncertain about which unit the disk space should be aligned with? section or zone?
>>
>> It looks like commit "e9dfbbb"(mkfs.f2fs: introduce zone align for main area)
>>
>> from Yunlei had changed the aligning unit from section to zone.
>>
>> So, should segment_count in superblock be aligned with zone rather than section?
> 
> I'm afraid that my codes of mkfs is too old, it doesn't contain this patch, and it still
> uses section size to align main area.
> 

Yeah, this patch is contained on dev branch, not yet on master:)

> Of course if main area should be aligned with zone, the following patch should be
> modified accordingly.
> 
>>
>> Thanks,
>>
>> Junling
>>
>>> mount will fail due to following condition:
>>>
>>> main_blkaddr + (segment_count_main << log_blocks_per_seg) !=
>>> 		segment0_blkaddr + (segment_count << log_blocks_per_seg)
>>>
>>> this is because when the length of main area isn't aligned with
>>> section, mkfs didn't add the number of excess segments to
>>> segment_count_main, but add it to segment_count.
>>> Here align segment_count with section size first to prevent such problem.
>>>
>>> Signed-off-by: Fan Li <fanofcode.li@samsung.com>
>>> ---
>>>  mkfs/f2fs_format.c |    3 ++-
>>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/mkfs/f2fs_format.c b/mkfs/f2fs_format.c index
>>> 66d7342..3366302 100644
>>> --- a/mkfs/f2fs_format.c
>>> +++ b/mkfs/f2fs_format.c
>>> @@ -174,7 +174,8 @@ static int f2fs_prepare_super_block(void)
>>>         }
>>>
>>>         set_sb(segment_count, (config.total_sectors * config.sector_size -
>>> -                               zone_align_start_offset) / segment_size_bytes);
>>> +                               zone_align_start_offset) / segment_size_bytes /
>>> +                               config.segs_per_sec *
>>> + config.segs_per_sec);
>>>
>>>         set_sb(segment0_blkaddr, zone_align_start_offset / blk_size_bytes);
>>>         sb->cp_blkaddr = sb->segment0_blkaddr;
>>>
>>
> 
> 
> 
> .
> 



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

  reply	other threads:[~2016-02-04  9:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03  5:29 [PATCH v2] f2fs-tools: set segment_count in super block correctly Fan Li
2016-02-04  2:51 ` Junling Zheng
2016-02-04  9:33   ` Fan Li
2016-02-04  9:53     ` Junling Zheng [this message]
2016-02-06  4:08     ` Jaegeuk Kim
2016-02-24  7:57       ` Fan Li
2016-02-24  8:33         ` Junling Zheng
2016-03-01  5:58           ` Fan Li
2016-03-01  6:27             ` Junling Zheng

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=56B31F8C.8050800@huawei.com \
    --to=zhengjunling@huawei.com \
    --cc=fanofcode.li@samsung.com \
    --cc=heyunlei@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.