archive mirror
 help / color / mirror / Atom feed
From: Ken Bass <>
Subject: [linux-lvm] Problem with partially activate logical volume
Date: Mon, 25 Jul 2022 09:48:22 -0500	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 909 bytes --]

(fwiw: I am new to this list, so please bear with me.)

Background: I have a very large (20TB) logical volume consisting of 3
drives. One of those drives unexpectedloy died (isn't that always the case
:-)). The drive that failed happened to be the last PV. So I am assuming
that there is still 2/3 of the data still intact and, to some extent,
recoverable. Although, apparently the ext4 fs is not recognised.

I activated the LV partially (via -P). But running any utility on that (eg:
dumpe2fs, e2fsck, ...) I get many of these  in dmesg:

"Buffer I/O error on dev dm-0, logical block xxxxxxx, async page read."
The thing is, the xxxxxxx block is on the missing drive/pv.

I have also tried some recovery software, but eventually get these same
messages, and the data recovered is not really useful.

Please help! How can I get passed that dmesg error, and move on. 14TB
recovered is better than 0.


[-- Attachment #1.2: Type: text/html, Size: 1156 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

linux-lvm mailing list
read the LVM HOW-TO at

             reply	other threads:[~2022-07-26  8:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 14:48 Ken Bass [this message]
2022-07-26  8:50 ` [linux-lvm] Problem with partially activate logical volume Roger James
2022-07-27 10:49   ` Roger Heflin
2022-07-27 11:26     ` Roger James
2022-08-03 21:31       ` Ken Bass
2022-08-04 11:07         ` Roger Heflin
2022-08-05 12:03         ` Zdenek Kabelac
2022-08-05 12:42           ` Ken Bass
2022-07-27 19:56 ` Zdenek Kabelac

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).