From: Ivan Sizov <sivan606@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>, Ivan Sizov <sivan606@gmail.com>,
Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Strange behavior after "rm -rf //"
Date: Mon, 8 Aug 2016 22:00:59 +0300 [thread overview]
Message-ID: <CAMG9ccw9meTUSoH9DVoa7zuhxR-q5N_2W3ULMWFGk7AbnHzKDQ@mail.gmail.com> (raw)
In-Reply-To: <20160808185237.GA9644@carfax.org.uk>
2016-08-08 21:52 GMT+03:00 Hugo Mills <hugo@carfax.org.uk>:
> On Mon, Aug 08, 2016 at 09:38:28PM +0300, Ivan Sizov wrote:
>> P.S. IMHO, log replay by default is a quite dangerous thing. I didn't
>> know about that change and I could lose all files if the live USB had
>> 4.6 kernel))
>
> Log reply on mount has _always_ been the default, and should remain
> so. It gives you the expected semantics after a power loss: all th
> efiles that you'd written up to the point of the power loss actually
> appear afterwards. (If this didn't happen, you could lose up to 30s of
> writes from before the crash).
>
> It's only very recently that there's been an option to prevent it,
> which is useful in a limited number of cases (such as trying to
> undelete a file, which is not really a supported operation in any
> case).
I mean only RO mount, of course.
So, will zero-log prevent my files during RW mount?
--
Ivan Sizov (SIvan)
next prev parent reply other threads:[~2016-08-08 19:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 16:30 Strange behavior after "rm -rf //" Ivan Sizov
2016-08-08 17:13 ` Chris Murphy
2016-08-08 18:38 ` Ivan Sizov
2016-08-08 18:52 ` Hugo Mills
2016-08-08 19:00 ` Ivan Sizov [this message]
2016-08-09 17:10 ` Chris Murphy
2016-08-09 20:30 ` Duncan
2016-08-21 17:54 ` Ivan Sizov
2016-08-08 19:02 ` Duncan
2016-08-09 23:24 ` Christian Kujau
2016-08-12 3:08 ` Russell Coker
2016-08-12 6:15 ` Christian Kujau
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=CAMG9ccw9meTUSoH9DVoa7zuhxR-q5N_2W3ULMWFGk7AbnHzKDQ@mail.gmail.com \
--to=sivan606@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).