public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Nikolay Borisov <nborisov@suse.com>
Cc: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: convert, warn if converting a fs which won't mount
Date: Fri, 28 Feb 2020 15:17:34 +0500	[thread overview]
Message-ID: <20200228151734.34512da4@natsu> (raw)
In-Reply-To: <291710b7-9218-da54-dbb5-391f6e106984@suse.com>

On Fri, 28 Feb 2020 10:13:41 +0200
Nikolay Borisov <nborisov@suse.com> wrote:

> 
> 
> On 28.02.20 г. 10:03 ч., Anand Jain wrote:
> > On aarch64 with pagesize 64k, btrfs-convert of ext4 is successful,
> > but it won't mount because we don't yet support subpage blocksize/
> > sectorsize.
> > 
> >  BTRFS error (device vda): sectorsize 4096 not supported yet, only support 65536
> > 
> > So in this case during convert provide a warning and a 10s delay to
> > terminate the command.
> > 
> > For example:
> > 
> > WARNING: Blocksize 4096 is not equal to the pagesize 65536,
> >          converted filesystem won't mount on this system.
> >          The operation will start in 10 seconds. Use Ctrl-c to stop it.
> > 10 9 8 7 6 5 4^C
> 
> What's the point of the delay? Just refuse to start the operation and quit.

IMO there should be a way to proceed with convert, if the user knows what they
are doing; maybe refuse the operation, but provide an "-f" "--force" option to
proceed anyway?

As for these 10 second delays, they always seemed a bit odd and unusual among
Linux filesystem tools or Unix CLI software in general.

-- 
With respect,
Roman

  reply	other threads:[~2020-02-28 10:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28  8:03 [PATCH] btrfs-progs: convert, warn if converting a fs which won't mount Anand Jain
2020-02-28  8:13 ` Nikolay Borisov
2020-02-28 10:17   ` Roman Mamedov [this message]
2020-02-28  8:27 ` Qu Wenruo
2020-02-28  9:06   ` Anand Jain
2020-02-28  9:11     ` Qu Wenruo
2020-03-03 17:44     ` David Sterba
2020-03-04  2:14       ` Anand Jain
2020-03-04  2:55         ` Qu Wenruo
2020-03-04 13:32         ` David Sterba
2020-03-04 15:22           ` Anand Jain

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=20200228151734.34512da4@natsu \
    --to=rm@romanrm.net \
    --cc=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    /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