All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Bruno Haible <bruno@clisp.org>
Cc: Evgeniy Dushistov <dushistov@mail.ru>, linux-fsdevel@vger.kernel.org
Subject: Re: ufs filesystem cannot mount NetBSD/arm64 partition
Date: Mon, 15 Jan 2024 22:33:00 +0000	[thread overview]
Message-ID: <20240115223300.GI1674809@ZenIV> (raw)
In-Reply-To: <20240115222220.GH1674809@ZenIV>

On Mon, Jan 15, 2024 at 10:22:20PM +0000, Al Viro wrote:
> On Mon, Jan 15, 2024 at 11:05:51PM +0100, Bruno Haible wrote:
> 
> > Whereas this partition can be mounted fine on FreeBSD, NetBSD, OpenBSD.
> > FreeBSD 11:
> > # mount -r -t ufs /dev/ada1s2 /mnt
> > NetBSD 9.3:
> > # mount -r -t ffs /dev/wd1a /mnt
> > OpenBSD 7.4:
> > # mount -r -t ffs /dev/wd1j /mnt
> > 
> > The source code line which emits the
> >   ufs: ufs_fill_super(): fragment size 8192 is too large
> > error is obviously linux/fs/ufs/super.c:1083.
> 
> Lovely...  Does it really have 8Kb fragments?  That would be painful
> to deal with - a plenty of places in there assume that fragment fits
> into a page...

FWIW, theoretically it might be possible to make that comparison with
PAGE_SIZE instead of 4096 and require 16K or 64K pages for the kernel
in question; that ought to work, modulo bugs in completely untested
cases ;-/

Support with 4K pages is a different story - that would take much
more surgery in fs/ufs.

Constraints:
	* fragment and block sizes are powers of 2.
	* block:fragment is 1, 2, 4 or 8.
Violating those is not an option for any kernel.
	* fragment fits into page.
Could be worked around, but not easily.

BTW, can NetBSD/i386 mount the same image?

  reply	other threads:[~2024-01-15 22:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 22:05 ufs filesystem cannot mount NetBSD/arm64 partition Bruno Haible
2024-01-15 22:22 ` Al Viro
2024-01-15 22:33   ` Al Viro [this message]
2024-01-15 23:08     ` Matthew Wilcox
2024-01-15 23:25       ` Al Viro
2024-01-15 23:29       ` Bruno Haible
2024-01-15 23:36         ` Al Viro
2024-01-15 23:28     ` Bruno Haible

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=20240115223300.GI1674809@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=bruno@clisp.org \
    --cc=dushistov@mail.ru \
    --cc=linux-fsdevel@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
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.