Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1202363

Re: [PATCH 0/4] loop: enable different physical blocksizes

From Ming Lei <tom.leiming@gmail.com>
Newsgroups linux.kernel
Subject Re: [PATCH 0/4] loop: enable different physical blocksizes
Date 2015-08-07 09:30 +0200
Message-ID <pUKgi-10c-15@gated-at.bofh.it> (permalink)
References <pN8fL-74a-7@gated-at.bofh.it> <pQO8O-7zV-13@gated-at.bofh.it> <pTx1M-Kt-11@gated-at.bofh.it> <pUI4N-6f4-3@gated-at.bofh.it> <pUJDz-8l4-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Fri, Aug 7, 2015 at 2:46 AM, Hannes Reinecke <hare@suse.de> wrote:
> On 08/07/2015 07:07 AM, Ming Lei wrote:
>> On Mon, Aug 3, 2015 at 7:00 PM, Alexander Graf <agraf@suse.de> wrote:
>>>
>
> [ .. ]
>
>>>
>>> because the guest thinks the disk is formatted with 4k sector size,
>>> while mkfs thought it's formatted with 512 byte sector size.
>>
>> I am wondering if mkfs is remembering the sector size of actual block
>> device, and at least it can't be found by 'dumpe2fs'. And it shouldn't have
>> do that, otherwise it isn't flexible. And one fs image often can be looped
>> successully by loop because loop's block size is 512.
>>
>> That is why I am wondering if we need support other logical block size
>> for loop.
>>
> If you were to install a bootloader (like lilo or zipl for S/390) it
> needs to write the _physical_ block addresses of the kernel and the
> initrd. And these do vary, depending in the physical blocksize.

So there isn't filesystem involved in your case of installing bootloader,
then I am wondering why you don't write the data to the backing block
directly? And why does loop have to be involved in this special case?

> So while the filesystems indeed do not care (all translation is done
> in the block driver, not the filesystem), bootloaders most certainly
> do.
> If you were to create a bootable disk on 4k disks you need this patch.

It it were me, I choose to do that against the disk directly, instead of
using loop, :-)


Thanks,
Ming Lei
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH 0/4] loop: enable different physical blocksizes Ming Lei <tom.leiming@gmail.com> - 2015-08-07 07:10 +0200
  Re: [PATCH 0/4] loop: enable different physical blocksizes Hannes Reinecke <hare@suse.de> - 2015-08-07 08:50 +0200
    Re: [PATCH 0/4] loop: enable different physical blocksizes Ming Lei <tom.leiming@gmail.com> - 2015-08-07 09:30 +0200
      Re: [PATCH 0/4] loop: enable different physical blocksizes Hannes Reinecke <hare@suse.de> - 2015-08-07 09:50 +0200
        Re: [PATCH 0/4] loop: enable different physical blocksizes Ming Lei <tom.leiming@gmail.com> - 2015-08-07 10:10 +0200

csiph-web