archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <>
To: LVM general discussion and development <>,
	Ken Bass <>
Subject: Re: [linux-lvm] Problem with partially activate logical volume
Date: Wed, 27 Jul 2022 21:56:27 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dne 25. 07. 22 v 16:48 Ken Bass napsal(a):
> (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.

Loosing such a large portion of device is always going to be a BIG problem.
Filesystem spreads metadata all over the place -  ExtX is somewhat better then 
BTree based FS like  XFS,BTRFS and may give you lot of your data back.

But that's why people should never underestimate how important is to keep 
reasonable fresh backups of their data - otherwise sooner or later there comes 
lesson like this one.

What you could try is to 'add' new PV to VG and use space for taking snapshot 
of your LV you want to repair - but this is somewhat complicated as you need 
to 'fix' VG first - which would ideally need to have some size of storage you 
just lost - but this gives you then fairly easy way forward.
(one way to do this is to use even 'virtual' storage over the loop back device 
- but that's for likely skilled admin.)

Lvm2 partial activation is designed to be used in a way to ACTIVATE LV - and 
copy the content to better/safe/secure location and there start to recover the 

Repairing storage in-place is usually straight road to hell - as there could 
be numerous way of recovery to try - but if your 1st. try actually destroys 
data even more, you can't retry with different strategy.

So depending on how much money and time you want to put into recovery of your 
data there are several different strategies possible  - considering storage 
space is relatively 'cheap' if your are data are really important.



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

      parent reply	other threads:[~2022-07-27 19:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 14:48 [linux-lvm] Problem with partially activate logical volume Ken Bass
2022-07-26  8:50 ` 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 [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:

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