From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 214927] re-mount read-write (mount -oremount,rw) of read-only filesystem rejected with EROFS, but block device is not read-only
Date: Wed, 03 Nov 2021 10:06:19 +0000 [thread overview]
Message-ID: <bug-214927-13602-jdSDZcum15@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214927-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214927
--- Comment #2 from Ulrich.Windl (Ulrich.Windl@rz.uni-regensburg.de) ---
Having a second look, it seems the first error was concurrently with fstrim, so
possibly fstrim can play a role in the scenario:
kernel: print_req_error: I/O error, dev xvdb, sector 29730024
fstrim[8864]: fstrim: /var: FITRIM ioctl failed: Input/output error
fstrim[8864]: fstrim: /tmp: FITRIM ioctl failed: Input/output error
...
(the final message was like 13 minutes after those above)
--
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 prev parent reply other threads:[~2021-11-03 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 9:49 [Bug 214927] New: re-mount read-write (mount -oremount,rw) of read-only filesystem rejected with EROFS, but block device is nor read-only bugzilla-daemon
2021-11-03 9:49 ` [Bug 214927] re-mount read-write (mount -oremount,rw) of read-only filesystem rejected with EROFS, but block device is not read-only bugzilla-daemon
2021-11-03 9:58 ` bugzilla-daemon
2021-11-03 10:06 ` bugzilla-daemon [this message]
2021-11-03 15:13 ` 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-214927-13602-jdSDZcum15@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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