All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 214551] Roll-Forward recovery recover deleted file
Date: Tue, 28 Sep 2021 15:27:35 +0000	[thread overview]
Message-ID: <bug-214551-202145-5Jewt5tjzW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214551-202145@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=214551

Chao Yu (chao@kernel.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |chao@kernel.org

--- Comment #1 from Chao Yu (chao@kernel.org) ---
(In reply to li jiazi from comment #0)
> reproduce step:
> dd if=/dev/zero of=test count=256
> fsync test
> rm test
> Trigger an abnormal reboot immediately.
> 
> After successful reboot, from dmesg, we can see f2fs recover this deleted
> test file:

If you want to see the status that file has been deleted after recovery,
you must call fsync on parent directory of test before SPO.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2021-09-28 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28  6:29 [f2fs-dev] [Bug 214551] New: Roll-Forward recovery recover deleted file bugzilla-daemon
2021-09-28 15:27 ` bugzilla-daemon [this message]
2021-12-12  4:08 ` [f2fs-dev] [Bug 214551] " bugzilla-daemon

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=bug-214551-202145-5Jewt5tjzW@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.