From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 198923] Linux 4.15.4+: Write on Ext4 causes system block
Date: Wed, 08 Nov 2023 09:37:23 +0000 [thread overview]
Message-ID: <bug-198923-11613-LbG11Qg34v@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198923-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198923
Javier Crosby (murphyde835@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |murphyde835@gmail.com
--- Comment #11 from Javier Crosby (murphyde835@gmail.com) ---
I'm encountering comparative issues as of late when rhythmbox(a case catcher)
is attempting to compose a downloaded mp3 record to a ntfs volume. Framework
isn't completely hindered however, just all further access endeavors (source:
https://coreball.co) to that ntfs volume fall flat during that meeting and upon
closure, the framework hangs tight for Circle Director for over 10 minutes
(didn't stand by significantly longer and did a hard reset).
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next parent reply other threads:[~2023-11-08 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-198923-11613@https.bugzilla.kernel.org/>
2023-11-08 9:37 ` bugzilla-daemon [this message]
2023-11-11 0:55 ` [Bug 198923] Linux 4.15.4+: Write on Ext4 causes system block bugzilla-daemon
2024-01-22 0:33 ` bugzilla-daemon
2024-04-20 7:18 ` bugzilla-daemon
2024-05-13 10:09 ` bugzilla-daemon
2024-05-13 10:49 ` bugzilla-daemon
2024-05-13 23:22 ` bugzilla-daemon
2024-05-21 9:29 ` 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-198923-11613-LbG11Qg34v@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-scsi@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 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.