From: Roman Mamedov <rm@romanrm.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Weird behavior (no commit?) when writing to a really slow block device
Date: Sun, 8 Jan 2023 05:59:50 +0500 [thread overview]
Message-ID: <20230108055950.2625fd86@nvm> (raw)
In-Reply-To: <20230108020331.3491fb52@nvm>
On Sun, 8 Jan 2023 02:03:31 +0500
Roman Mamedov <rm@romanrm.net> wrote:
> if there was a complete flush of data and metadata. And I suspect issuing a
> "sync" on command-line would cause that to occur.
In fact, no. :D
Running a "sync" simply does not return while the rsync process is still
actively copying data to the slow device.
It's stuck for 30 minutes by now, despite it would take less than 4 minutes to
write out the 3.5 GB of the writeback buffer at 15 MB/sec of the target device.
And the free space in "df" still did not update from what it was when I started
the copy process 3 hours ago. rsync has managed to write 185 GB since then,
according to its /proc/xxx/io.
--
With respect,
Roman
prev parent reply other threads:[~2023-01-08 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 21:03 Weird behavior (no commit?) when writing to a really slow block device Roman Mamedov
2023-01-08 0:59 ` Roman Mamedov [this message]
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=20230108055950.2625fd86@nvm \
--to=rm@romanrm.net \
--cc=linux-btrfs@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