Linux-Raid Archives on lore.kernel.org
 help / color / Atom feed
From: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
To: linux-raid@vger.kernel.org
Subject: Problem with initial sync of a RAID1 with 4Kn drives
Date: Fri, 29 Jan 2021 21:31:29 +0100
Message-ID: <87ddf15f-e133-47b4-32f6-64a8c7b9d993@math.uni-bielefeld.de> (raw)

Hello folks,

I recently got two new Seagate drives, Seagate Exos X X16, which are 
able to switch into native 4K mode. I used the Seagate tools to trigger 
the switch, and now want to use the two drives in a RAID1.

I proceeded to create the md device:
mdadm --create --verbose --level=1 --metadata=1.2 --raid-devices=2 
/dev/md/onyx-new /dev/sda /dev/sdb

As soon as the initial sync starts the kernel log begins to fill up with 
errors. Here's part of the kernel log:
https://gist.github.com/tobiasjakobi/d5b5f1638d23765d5e1fecf0dfbcea3e

This is a 5.10.11 vanilla kernel, but it also happens with the 5.9.y 
series. As you can see I already patched the kernel to include 
additional information:
DEBUG: 40801 1 7

This is just a simple print() in sd_setup_read_write_cmnd().
printk("DEBUG: %x %x %x\n", blk_rq_pos(rq), blk_rq_sectors(rq), mask);

So it seems that neither the position nor the number of sectors is 
aligned to eight. I assume that the md subsystem is supposed to handle this?

I then double-checked for sizes for the underlying block devices and the 
md device itself:
cat 
/sys/block/{sda,sdb,md126}/queue/{hw_sector_size,logical_block_size,physical_block_size}
4096

So it's 4K for all of them.

Here's the hdparm output for one of the drives:
https://gist.github.com/tobiasjakobi/a52cf5d4461db35c1f474c6a69b0782a

The drives themselves are fine, I can use them properly as standalone 
devices, so I rule out a hardware error.

Any hints how to further triage this? Also would it help to open a bug 
on the kernel bugtracker?

Thanks in advance!

With best wishes,
Tobias Jakobi


                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87ddf15f-e133-47b4-32f6-64a8c7b9d993@math.uni-bielefeld.de \
    --to=tjakobi@math.uni-bielefeld.de \
    --cc=linux-raid@vger.kernel.org \
    /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

Linux-Raid Archives on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-raid/0 linux-raid/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-raid linux-raid/ https://lore.kernel.org/linux-raid \
		linux-raid@vger.kernel.org
	public-inbox-index linux-raid

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-raid


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git