From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Chao Yu <chao@kernel.org>
Subject: Re: Multidevice f2fs mount after disk rearrangement
Date: Mon, 06 Jan 2020 19:40:55 +0100 [thread overview]
Message-ID: <ee2cb1d7a6c1b51e1c8277a8feaafe6d@natalenko.name> (raw)
In-Reply-To: <20200106183450.GC50058@jaegeuk-macbookpro.roam.corp.google.com>
Hi.
On 06.01.2020 19:34, Jaegeuk Kim wrote:
> Thank you for investigating this ahead of me. :) Yes, the device list
> is stored
> in superblock, so hacking it manually should work.
>
> Let me think about a tool to tune that.
Thank you both for the replies.
IIUC, tune.f2fs is not there yet. I saw a submission, but I do not see
it as accepted, right?
Having this in tune.f2fs would be fine (assuming the assertion is
replaced with some meaningful hint message), but wouldn't it be more
convenient for an ordinary user to have implemented something like:
# mount -t f2fs /dev/sdb -o nextdev=/dev/sdc /mnt/fs
Hm?
--
Oleksandr Natalenko (post-factum)
next prev parent reply other threads:[~2020-01-06 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 16:29 Oleksandr Natalenko
2020-01-04 21:52 ` Oleksandr Natalenko
2020-01-06 3:41 ` [f2fs-dev] " Chao Yu
2020-01-06 18:40 ` Jaegeuk Kim
2020-01-08 8:37 ` Chao Yu
2020-01-06 18:34 ` Jaegeuk Kim
2020-01-06 18:40 ` Oleksandr Natalenko [this message]
2020-01-08 8:52 ` [f2fs-dev] " Chao Yu
2020-01-08 12:00 ` Jaegeuk Kim
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=ee2cb1d7a6c1b51e1c8277a8feaafe6d@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome