From: Christoph Hellwig <hch@infradead.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Daeho Jeong <daeho43@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Daeho Jeong <daehojeong@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v5] f2fs: introduce device aliasing file
Date: Mon, 14 Oct 2024 22:05:12 -0700 [thread overview]
Message-ID: <Zw34CMxJB-THlGW0@infradead.org> (raw)
In-Reply-To: <Zw1J30Fn48uYCwK7@google.com>
On Mon, Oct 14, 2024 at 04:42:07PM +0000, Jaegeuk Kim wrote:
> >
> > Plz, refer to this patch and the description there.
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/commit/?h=dev-test&id=8cc4e257ec20bee207bb034d5ac406e1ab31eaea
>
> Also, I added this in the description.
>
> ---
> For example,
> "mkfs.f2fs -c /dev/block/test@test_alias /dev/block/main" gives
> a file $root/test_alias which carves out /dev/block/test partition.
What partition?
So mkfs.f2fs adds additional devices based on the man page.
So the above creates a file system with two devices, but the second
device is not added to the general space pool, but mapped to a specific
file? How does this file work. I guess it can't be unlinked and
renamed. It probably also can't be truncated and hole punched,
or use insert/collapse range. How does the user find out about this
magic file? What is the use case? Are the exact semantics documented
somewhere?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Daeho Jeong <daehojeong@google.com>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, kernel-team@android.com
Subject: Re: [f2fs-dev] [PATCH v5] f2fs: introduce device aliasing file
Date: Mon, 14 Oct 2024 22:05:12 -0700 [thread overview]
Message-ID: <Zw34CMxJB-THlGW0@infradead.org> (raw)
In-Reply-To: <Zw1J30Fn48uYCwK7@google.com>
On Mon, Oct 14, 2024 at 04:42:07PM +0000, Jaegeuk Kim wrote:
> >
> > Plz, refer to this patch and the description there.
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/commit/?h=dev-test&id=8cc4e257ec20bee207bb034d5ac406e1ab31eaea
>
> Also, I added this in the description.
>
> ---
> For example,
> "mkfs.f2fs -c /dev/block/test@test_alias /dev/block/main" gives
> a file $root/test_alias which carves out /dev/block/test partition.
What partition?
So mkfs.f2fs adds additional devices based on the man page.
So the above creates a file system with two devices, but the second
device is not added to the general space pool, but mapped to a specific
file? How does this file work. I guess it can't be unlinked and
renamed. It probably also can't be truncated and hole punched,
or use insert/collapse range. How does the user find out about this
magic file? What is the use case? Are the exact semantics documented
somewhere?
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-10-15 5:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 19:26 [f2fs-dev] [PATCH v5] f2fs: introduce device aliasing file Daeho Jeong
2024-10-10 19:26 ` Daeho Jeong
2024-10-12 2:40 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2024-10-12 2:40 ` Chao Yu
2024-10-14 5:56 ` [f2fs-dev] " Christoph Hellwig
2024-10-14 5:56 ` Christoph Hellwig
2024-10-14 16:28 ` [f2fs-dev] " Daeho Jeong
2024-10-14 16:28 ` Daeho Jeong
2024-10-14 16:42 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2024-10-14 16:42 ` Jaegeuk Kim
2024-10-15 5:05 ` Christoph Hellwig [this message]
2024-10-15 5:05 ` Christoph Hellwig
2024-10-15 16:56 ` Jaegeuk Kim
2024-10-15 16:56 ` Jaegeuk Kim via Linux-f2fs-devel
2024-10-15 5:02 ` Christoph Hellwig
2024-10-15 5:02 ` Christoph Hellwig
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=Zw34CMxJB-THlGW0@infradead.org \
--to=hch@infradead.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.