linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henk Slager <eye1tm@gmail.com>
To: Simeon Felis <simeon_btrfs@sfelis.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel incompatibility?
Date: Tue, 18 Feb 2020 12:54:17 +0100	[thread overview]
Message-ID: <CAPmG0ja40xPPcXxM+uv_v339v+8Jc5TLP_kONbkw1vWHFUer-Q@mail.gmail.com> (raw)
In-Reply-To: <8fb8442b-dbf9-4d4b-42bb-ce460048f891@sfelis.de>

On Sun, Feb 16, 2020 at 10:29 AM Simeon Felis <simeon_btrfs@sfelis.de> wrote:
> [1] https://lists.archlinux.org/pipermail/arch-general/2020-February/047463.html
The partition size calculations done in the reference are not correct,
they are 1 512-byte-sized sector too smal (compare: if start_sector=0,
end_sector=9, size is 10).

Then still, there are some other errors somewhere, that might be
triggered by having unequeal sized partitions sdb1 and sdc1
You could look at backports w.r.t. 32-bit vs. 64-bit, maybe related to
changes 512 sector sizes and 4k page sizes. And better use gdisk
instead of fdisk I think. And maybe check first 1MiB and last 2MiB of
both disks.
There are also Ubuntu 32-bit and 64-bit images available for
RaspberryPi's with kernel 5.3.x, maybe that gives hints where the
root-cause is.

  parent reply	other threads:[~2020-02-18 11:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16  9:02 kernel incompatibility? Simeon Felis
2020-02-17 22:55 ` Chris Murphy
2020-02-18  2:14   ` Adam Borowski
2020-02-18 11:54 ` Henk Slager [this message]
2020-02-18 14:15   ` Chris Murphy
2020-02-18 17:20     ` Henk Slager
2020-02-18 17:22       ` Henk Slager

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=CAPmG0ja40xPPcXxM+uv_v339v+8Jc5TLP_kONbkw1vWHFUer-Q@mail.gmail.com \
    --to=eye1tm@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=simeon_btrfs@sfelis.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).