ntfs3.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Sebastian Eifert <eifert@gmail.com>
To: ntfs3@lists.linux.dev
Subject: Bonnie++ failure with ntfs3
Date: Thu, 23 Sep 2021 18:53:45 +0200	[thread overview]
Message-ID: <CAOZgwEd7NDkGEpdF6UQTcbYuupDavaHBoj4WwTy3Qe4Bqm6V0g@mail.gmail.com> (raw)

Hi,

I'm currently trying out ntfs3 (v27 from the mailing list, 5.15-rc2,
and current master from the Paragon github repo) with the good old
Bonnie++ benchmark (1.04), and I'm seeing a hard failure:

<console>
/mnt/ntfs4gb # bonnie\+\+ -u root -s 64 -r 32
Using uid:0, gid:0.
Writing with putc()...done
Writing intelligently...done
Rewriting...done
Reading with getc()...done
Reading intelligently...done
start 'em...done...done...done...
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...
Bonnie: drastic I/O error (rmdir): Directory not empty
Cleaning up test directory after error.
</console>

Environment is an AARCH64 embedded platform, with a 4GB NTFS image
file mounted via a loopback device.

Could someone try Bonnie++ on a different setup and confirm/reject my result?

I hacked around in Bonnie a bit, and it turns out that the directory
traversal with opendir/readdir is not enumerating all files that were
created just before. Running the default 1024 test files, I'm seeing
~20 files not enumerating. Adding a sleep before opendir/readdir does
not change the result. However, doing a second opendir/readdir
enumeration immediately after the first *will* enumerate all files.

Thanks,
Sebastian

                 reply	other threads:[~2021-09-23 16:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAOZgwEd7NDkGEpdF6UQTcbYuupDavaHBoj4WwTy3Qe4Bqm6V0g@mail.gmail.com \
    --to=eifert@gmail.com \
    --cc=ntfs3@lists.linux.dev \
    /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).