mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vyacheslav Kovalevsky <slava.kovalevskiy.2014@gmail.com>
To: clm@fb.com, dsterba@suse.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Directory is not persisted after writing to the file within directory if system crashes
Date: Fri, 24 Oct 2025 18:19:05 +0300	[thread overview]
Message-ID: <03c5d7ec-5b3d-49d1-95bc-8970a7f82d87@gmail.com> (raw)

Under some circumstances, directory entry is not persisted after writing 
to the file inside the directory that was opened with `O_SYNC` flag if 
system crashes.


Detailed description
====================

Hello, we have found another issue with btrfs crash behavior.

In short, empty file is created and synced. Then, a new directory is 
created, old file is opened with `O_SYNC` flag and some data is written. 
After this, a new hard link is created inside the directory and the root 
is `fsync`ed (directory should persist). However, after a crash, the 
directory entry is missing even though data written to the old file was 
persisted.


System info
===========

Linux version 6.18.0-rc2, also tested on 6.14.11.


How to reproduce
================

```
#include <errno.h>
#include <fcntl.h>
#include <stdio.h>
#include <string.h>
#include <sys/stat.h>
#include <sys/types.h>
#include <unistd.h>

int main() {
int status;
int file_fd;
int root_fd;

status = creat("file1", S_IRWXU | S_IRWXG | S_IROTH | S_IXOTH);
printf("CREAT: %d\n", status);

// persist `file1`
sync();

status = mkdir("dir", S_IRWXU | S_IRWXG | S_IROTH | S_IXOTH);
printf("MKDIR: %d\n", status);

status = open("file1", O_WRONLY | O_SYNC);
printf("OPEN: %d\n", status);
file_fd = status;

status = write(file_fd, "Test data!", 10);
printf("WRITE: %d\n", status);

status = link("file1", "dir/file2");
printf("LINK: %d\n", status);

status = open(".", O_RDONLY | O_DIRECTORY);
printf("OPEN: %d\n", status);
root_fd = status;

// persist `dir`
status = fsync(root_fd);
printf("FSYNC: %d\n", status);
}
```

Steps:

1. Create and mount new btrfs file system in default configuration.
2. Change directory to root of the file system and run the compiled test.
3. Cause hard system crash (e.g. QEMU `system_reset` command).
4. Remount file system after crash.
5. Observe that `dir` directory is missing.

Notes:

- ext4 does persist `dir` and `dir/file2` even though it was not synced.
- xfs does persist `dir` but does not persist `dir/file2`.


P.S. Want to apologize for formatting in previous report, first time 
using Thunderbird and plain text.




             reply	other threads:[~2025-10-24 15:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24 15:19 Vyacheslav Kovalevsky [this message]
2025-10-24 16:17 ` Filipe Manana
2025-10-25  9:49   ` Vyacheslav Kovalevsky
2025-10-25 23:40     ` Chris Murphy
2025-10-26  9:04     ` Filipe Manana
2025-10-27  7:19       ` 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=03c5d7ec-5b3d-49d1-95bc-8970a7f82d87@gmail.com \
    --to=slava.kovalevskiy.2014@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®