From: "Chris Murphy" <lists@colorremedies.com>
To: "Vyacheslav Kovalevsky" <slava.kovalevskiy.2014@gmail.com>,
"Filipe Manana" <fdmanana@kernel.org>
Cc: "Chris Mason" <clm@fb.com>, "David Sterba" <dsterba@suse.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Directory is not persisted after writing to the file within directory if system crashes
Date: Sat, 25 Oct 2025 19:40:54 -0400 [thread overview]
Message-ID: <601d70f3-ab6d-4f15-88eb-169fede1a685@app.fastmail.com> (raw)
In-Reply-To: <d039a3c8-c4f7-487c-a848-2a26ea26f77d@gmail.com>
On Sat, Oct 25, 2025, at 5:49 AM, Vyacheslav Kovalevsky wrote:
> I think the line with `echo` may not be the correct translation:
> > echo -n "hello world" > $SCRATCH_MNT/file1
>
> In the original test, the file was opened with `O_SYNC` flag, if you
> remove it, the directory will be there when the system crashes. I also
> forgot to close the file after the `creat` call in the original test,
> may be important as well.
>
> The test itself is quite weird (why would `dir` be gone after seemingly
> unrelated operation?), any detail can matter.
>
> Please run the original test with a real system crash.
This would produce hardware specific results rather than determining whether the file system is behaving correctly. It's possible the hardware is acknowledging the metadata, flush, super, flush, but then it's still not really persisting on disk
--
Chris Murphy
next prev parent reply other threads:[~2025-10-25 23:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 15:19 Vyacheslav Kovalevsky
2025-10-24 16:17 ` Filipe Manana
2025-10-25 9:49 ` Vyacheslav Kovalevsky
2025-10-25 23:40 ` Chris Murphy [this message]
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=601d70f3-ab6d-4f15-88eb-169fede1a685@app.fastmail.com \
--to=lists@colorremedies.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava.kovalevskiy.2014@gmail.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
all inboxes | Powered by JetHome®