From: Mehrdad Dashtbani <mehrdad1374.md@gmail.com>
To: gfs2@lists.linux.dev
Subject: fsck.gfs2 bad read: Input/output error from lgfs2_inode_read:51
Date: Sat, 13 Jan 2024 12:52:08 +0330 [thread overview]
Message-ID: <CA+sT36sN+q6+a9JU4=ZLDVhcw+B6+YV4AE-MJZu6wNiXGssN6A@mail.gmail.com> (raw)
Hi, everyone
I have a cluster which is using GFS2 for shared storage.
Unexpectedly, an I/O error occurred on one of the cluster's nodes and
unfortunately I had to reboot the cluster's nodes. After everyone
booted up, GFS mounted successfully, however I/O error still persists
on the exact node.
Then I tried to resolve it by using fsck.gfs2. So storages were
unmounted and fsck was started to recover the filesystem.
Unluckily, in the middle of the recovery my SSH session was terminated
and so was the fsck command.
Now when I try to re-run the fsck.gfs2 again, an error is thrown:
bad read: Input/output error from lgfs2_inode_read:51: block
288230926779940864 (0x400008034000000) count: 1 size: 4096 ret: 0
Thanks,
Mehrdad
next reply other threads:[~2024-01-13 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 9:22 Mehrdad Dashtbani [this message]
2024-01-13 9:37 ` fsck.gfs2 bad read: Input/output error from lgfs2_inode_read:51 Mehrdad Dashtbani
2024-01-16 15:51 ` Andrew Price
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='CA+sT36sN+q6+a9JU4=ZLDVhcw+B6+YV4AE-MJZu6wNiXGssN6A@mail.gmail.com' \
--to=mehrdad1374.md@gmail.com \
--cc=gfs2@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 read-only IMAP folder(s) and NNTP newsgroup(s).