lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 30 Jul 2020 09:16:05 +1000
From:   Dave Chinner <david@...morbit.com>
To:     Takuya Yoshikawa <takuya.yoshikawa@...il.com>
Cc:     linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org
Subject: Re: ext4/xfs: about switching underlying 512B sector devices to 4K
 ones

On Wed, Jul 29, 2020 at 07:38:33PM +0900, Takuya Yoshikawa wrote:
> I have a question: is it possible to make existing ext4/xfs filesystems
> formatted on 512B sector devices run as is on 4k sector devices?
> 
> 
> Problem:
> 
> We are maintaining some legacy servers whose data is stored on
> ext4/xfs filesystems formatted on lvm2 raid1 devices.
> 
> These raid1 devices consist of a few iSCSI devices, so the
> remote storage servers running as iSCSI targets are the actual
> data storage.
> 
>   /dev/md127 --  /dev/sda  --(iSCSI)-- remote storage server
>                  /dev/sdb  --(iSCSI)-- remote storage server
> 
> A problem happened when we tried to add a new storage server with
> 4k sector disks as an iSCSI target. After lvm2 added that iSCSI
> device and started syncing the blocks from existing 512B sector
> storage servers to the new 4k sector ones, we got
> "Bad block number requested" messages, and soon after that,
> the new device was removed from the lvm2 raid1 device.
> 
>   /dev/md127 --  /dev/sda  --(iSCSI)-- remote storage server(512)
>                  /dev/sdb  --(iSCSI)-- remote storage server(512)
>               *  /dev/sdc  --(iSCSI)-- remote storage server(4k)
> 
>   The combined raid1 device had been recognized as a 4k device
>   as described in this article:
>     https://access.redhat.com/articles/3911611

Rule of thumb: growing must always be done with devices that have
the same or smaller logical sector sizes. IOWs, the above will break
any filesystem that is formatted with alignment to the logical
sector size of 512 bytes...

> It seemed like 512B unaligned requests from the xfs filesystem
> were sent to the raid1 device, and mirrored requests caused
> the problem on the newly added 4k sector storage.

Yes, because XFS has permanent metadata that is logical sector sized
and aligned. Hence if the device has a logical sector size of 512
at mkfs time, you will get this:

> The xfs was formatted with its sector_size_options set to the
> default (512).
> See https://www.man7.org/linux/man-pages/man8/mkfs.xfs.8.html

and that filesystem will not work on 4k physical/logical
storage devices.

if you start with 4k devices, mkfs.xfs will detect 4k
physical/logical devices and set it's sector size to 4k
automatically and hence will work on those devices, but you can't
change this retrospectively....

> xfs: is it possible to change the filesystem sector size?

Only at mkfs time.

Cheers,

Dave.

-- 
Dave Chinner
david@...morbit.com

Powered by blists - more mailing lists