From: Andreas Rohner <andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
To: Clemens Eisserer
<linuxhippy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 0/1] nilfs2: add mount option that reduces super block writes
Date: Mon, 10 Feb 2014 09:56:22 +0100 [thread overview]
Message-ID: <52F89436.7000202@gmx.net> (raw)
In-Reply-To: <CAFvQSYT0cdeETZX-qdq07t6T4jq9Z=wJxXwBzycyn9Ue_JV8FA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Clemens,
On 2014-02-09 16:36, Clemens Eisserer wrote:
> Hi Andreas, hi Ryusuke,
>
>> Instead of periodically writing to the super block, this patch only
>> writes at mount and umount time and performs a linear scan for the
>> latest segment in case a recovery is necessary.
>> The SD-Cards and the USB-Stick are not particularly fast, but they are
>> small enough so that the recovery time is tolerable.
>
> Finally I found some time to test your patch and also the new version
> works fine (and fast!) here:
>
> [ 3.349464] NILFS warning: searching for latest log
> [ 4.747552] NILFS warning: mounting unchecked fs
> [ 5.214883] NILFS: recovery complete.
>
> So your enhanced recovery code requires ~1.3s for a 12GB nilfs2
> partition on the higher-end 16GB SD card I use in the raspberry.
> Also, despite frequent power-cuts I haven't obsereved any issues -
> which made me switch to nilfs2+patch even for the rootfs (was ext4
> ro).
Thanks for testing it on your raspberry pi. I also own one, but I didn't
move the root fs to nilfs2 yet. Please be careful using the patch on a
production system. Although I am quite confident that it is safe, there
may still be some horrible bug in my code. More testing is definitely
necessary. It is not an "enhanced recovery" as you put it, but more like
a corner case experimental brute force recovery. Nevertheless I am
surprised how fast it is on the pi.
>> I see. For further discussion on this approach, it looks like we need
>> some measurement data of the situation that this patch makes a
>> difference (for example, for an SD card or some device). Anyway, I
>> agree that the patch has a value for experiment purpose.
>
> What do you think about the results obtained by andreas and me?
> With SD cards (in the raspberry) I experience linear scan times as low
> as ~110ms/1GB, and for everything else avoiding superblock writes
> probably doesn't make sense anyway. And if some techie enables the
> option on his SSD, recovery is also blazingly fast.
>
> Thanks a lot & best regards, Clemens
Best regards,
Andreas Rohner
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-02-10 8:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 16:50 [PATCH v2 0/1] nilfs2: add mount option that reduces super block writes Andreas Rohner
[not found] ` <cover.1391359219.git.andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
2014-02-02 16:50 ` [PATCH v2 1/1] " Andreas Rohner
[not found] ` <dd489a00bca481cea1cb69e755ed5db5b186a5e5.1391359219.git.andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
2014-02-05 20:21 ` Clemens Eisserer
2014-02-11 12:31 ` Ryusuke Konishi
[not found] ` <20140211.213138.107755196.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-02-11 14:07 ` Andreas Rohner
[not found] ` <52FA2EB4.6030401-hi6Y0CQ0nG0@public.gmane.org>
2014-02-11 18:11 ` Ryusuke Konishi
[not found] ` <20140212.031115.172542304.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-02-11 19:58 ` Andreas Rohner
[not found] ` <52FA80F5.1090003-hi6Y0CQ0nG0@public.gmane.org>
2014-02-12 0:58 ` Ryusuke Konishi
[not found] ` <20140212.095831.397309935.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-02-12 1:23 ` Ryusuke Konishi
2014-02-09 15:36 ` [PATCH v2 0/1] " Clemens Eisserer
[not found] ` <CAFvQSYT0cdeETZX-qdq07t6T4jq9Z=wJxXwBzycyn9Ue_JV8FA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-10 8:56 ` Andreas Rohner [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=52F89436.7000202@gmx.net \
--to=andreas.rohner-hi6y0cq0ng0@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxhippy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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