From: Chao Yu <chao@kernel.org>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: f2fs on top ov LV
Date: Sun, 4 Feb 2018 22:54:23 +0800 [thread overview]
Message-ID: <2d1573a8-f783-2c27-61ab-8de412993b04@kernel.org> (raw)
In-Reply-To: <20180202172947.GA3981@lazy.lzy>
Hi,
On 2018/2/3 1:29, Piergiorgio Sartor wrote:
> Hi all,
>
> I'm planning to prepare a Linux installation
> on an USB flash drive.
>
> The idea is to have /boot (with ext, since grub2
> does not support f2fs yet) and / with f2fs.
> Both on the USB flash drive while /home will be
> somewhere else.
>
> Now, I've a backup tool exploiting lvm snapshots
> and I would like to use it.
>
> This means / will be on top of an LV.
>
> Does it make any sense to have f2fs over lvm?
> Will still be some benefits from f2fs in this
> setup?
I think it's OK to build f2fs image based on lvm, and IMO, there
will be no difference when building image on lvm partition or raw
partition, since f2fs won't be aware of lvm.
>
> How about snapshots? Could they cause problems?
> Usually the filesystem mounted from lvm snapshot
> has consistency issues, which are they usually
> solved by journal.
> I guess f2fs should be fine, but I would like to
> confirm with experts here.
f2fs supports fsfreeze and roll-forward recovery, so I think
it's fine to use lvm snapshot on f2fs image.
>
> Of course, one possibility would be to use f2fs
> on the raw partition, waiting for snapshot to
> be implemented.
> What's the plan about this?
It's in todo list, but it's not critical for us to implement
this feature as in usual android scenario there is no strong
demand to use this feature.
Thanks,
>
> Thanks a lot for any answers,
>
> bye,
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
prev parent reply other threads:[~2018-02-04 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 17:29 f2fs on top ov LV Piergiorgio Sartor
2018-02-04 14:54 ` Chao Yu [this message]
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=2d1573a8-f783-2c27-61ab-8de412993b04@kernel.org \
--to=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=piergiorgio.sartor@nexgo.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).