From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 65DA1C19F2D for ; Thu, 4 Aug 2022 07:07:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1659596859; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post; bh=7roLCoHkfRLRKp3/n4ScrHl988AuemO+I4icc5COKgw=; b=XjO5QEMzKH7BL0dlxODnuyg81tNGZ2j7ZaX3PybW6CR6L+hk3Uz6QHbx42O70nA0UOu3t7 8mAQg8t5bQhf3wrIIV0n+rL+YTjz+3qWcvgyTXq1RtODq+lXLYEpW7q7dRzghx2YSw+etg cLwWEUDagD+pvUUxo9Utjf3KuE5HvBI= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-103-rC1-eNy7M5OdY4QR-JygeQ-1; Thu, 04 Aug 2022 03:07:35 -0400 X-MC-Unique: rC1-eNy7M5OdY4QR-JygeQ-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 09D128037B7; Thu, 4 Aug 2022 07:07:32 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 66BBC2026D07; Thu, 4 Aug 2022 07:07:28 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 38F151946A53; Thu, 4 Aug 2022 07:07:28 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 60D7C1946A53 for ; Wed, 3 Aug 2022 21:31:37 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 451BD40CFD0D; Wed, 3 Aug 2022 21:31:37 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast09.extmail.prod.ext.rdu2.redhat.com [10.11.55.25]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 40FA740CFD0A for ; Wed, 3 Aug 2022 21:31:37 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 25A45281137C for ; Wed, 3 Aug 2022 21:31:37 +0000 (UTC) Received: from mail-ej1-f49.google.com (mail-ej1-f49.google.com [209.85.218.49]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-516-nAQL-hmaM0mUcHNYKjbFzQ-1; Wed, 03 Aug 2022 17:31:35 -0400 X-MC-Unique: nAQL-hmaM0mUcHNYKjbFzQ-1 Received: by mail-ej1-f49.google.com with SMTP id tl27so15809603ejc.1 for ; Wed, 03 Aug 2022 14:31:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=I1gFAF+gHWSmBH5YwN8jbzs073zQNwS/xamTRtGFhSM=; b=WzYZnzP4UtUbTw0x8oj/PVjweCyH+2HlnCii+6p1BUFk0mv5MpQg/+9O1149q4rCpf kjYsXishHw2u3laG5168zwhP5YU02glP57wBXX6rwJNe7XaI/AnpB/ySYcCQv60IyICH 4HynEcbSNb7po9WF+t6JKSoRfWV/KQW0GvW8w6U5h0Eq8bwecK5MZIVQfn1bwX8qFKKm XNUNfwOrTPCd2TrY0begJEEwq7kmulfj3ecKu61a818hoH3ueARU4MPJt4xgOaCdJMAR NAdM+vaq0nnHCQzeGIgvhTwHlDzLBmKYZG2dSon8tJiMaaABOn3uQYKXDfemp+hBgVMy iqxw== X-Gm-Message-State: ACgBeo0CfgqbUL4uyXYKH8DNhswBcVjYu8jnlwZ/a70PXcdMlNbLkxZB f5WLGFH8Fs19bVZX6BAomCxhIE955LhtXlJvuzV9dBB4QM0= X-Google-Smtp-Source: AA6agR6cbGjchyAGMCQpJ2jMYCC6gRRUKuGApTCNdN67tVyPjqoFy87jRFQjQpcN+YLpD3zpC2tg3H0t90ZryzcWVpI= X-Received: by 2002:a17:907:2e01:b0:730:a098:7257 with SMTP id ig1-20020a1709072e0100b00730a0987257mr7814422ejc.705.1659562293628; Wed, 03 Aug 2022 14:31:33 -0700 (PDT) MIME-Version: 1.0 References: <18239b39270.27a5.d4b3b9aee17a85f6bc878c68b3925db6@beardandsandals.co.uk> <1823f6818f8.27a5.d4b3b9aee17a85f6bc878c68b3925db6@beardandsandals.co.uk> In-Reply-To: <1823f6818f8.27a5.d4b3b9aee17a85f6bc878c68b3925db6@beardandsandals.co.uk> From: Ken Bass Date: Wed, 3 Aug 2022 16:31:22 -0500 Message-ID: To: LVM general discussion and development X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.84 on 10.11.54.1 X-Mailman-Approved-At: Thu, 04 Aug 2022 07:07:27 +0000 Subject: Re: [linux-lvm] Problem with partially activate logical volume X-BeenThere: linux-lvm@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: LVM general discussion and development Errors-To: linux-lvm-bounces@redhat.com Sender: "linux-lvm" X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/mixed; boundary="===============0709183537405220882==" --===============0709183537405220882== Content-Type: multipart/alternative; boundary="000000000000fe91ba05e55cf442" --000000000000fe91ba05e55cf442 Content-Type: text/plain; charset="UTF-8" That's pretty much it. Whenever any app attempts to read a block from the missing drive, I get the "Buffer I/O error" message. So, even though my recovery apps can scan the LV, marking blocks on the last drive as missing/unknown/etc., they can't display any recovered data - which I know does exist. Looking at raw data from the apps' scans, I can see directory entries, as well as files. I'm sure the inodes and bitmaps are still there for some of these, I just can't really reverse engineer and follow them through. But isn't that what the apps are supposed to do? As for debugfs: pretty much the same issue: in order to use it, I need to open the fs. But that (in debugfs) fails as well. So it can't help much. Unless I'm missing something about debugfs. The one thing I haven't tried is to use vgreduce to remove the missing PV; but that will also remove the LV as well, which is why I haven't tried it yet. Sorry I haven't replied sooner, but it takes a long time (days) to clone, then scan 16Tb... So, please any suggestions are greatly appreciated, as well as needed. ken (I know: No backup; got burned; it hurts; and I will now always have backups. 'Nuf said.) On Thu, Jul 28, 2022 at 3:12 AM Roger James wrote: > The procedure outlined should at least get you back to a state where the > lv is consistent but with blank sectors where the data is missing. I would > suggest using dd to make a backup partition image. Then you can either work > on that or the original to mend the fs. > > On 27 July 2022 11:50:07 Roger Heflin wrote: > > I don't believe that is going to work. >> >> His issue is that the filesystem is refusing to work because of the >> missing data. >> >> man debugfs >> >> It will let you manually look at the metadata and structures of the >> ext2/3/4 fs. You will likely need to use the "-c" option. >> >> It will be very manual and you should probably read up on the fs >> structure a bit. >> >> A data recovery company could get most of the data back, but they >> charge 5k-10k per TB, so likely close to 100k US$. >> >> And the issues will be that 1/3 of the metadata was on the missing >> disk, and some of the data was on the missing disk. >> >> I was able to do debugfs /dev/sda2 (my /boot) and do an ls and list >> out the files and then do a dump /tmp/junk.out and copy out >> that file. >> >> So the issue will be writing up a script to do lses and find all of >> the files and dump all of the files to someplace else. >> >> On Wed, Jul 27, 2022 at 2:39 AM Roger James >> wrote: >> >>> >>> Try >>> https://www.linuxsysadmins.com/recover-a-deleted-physical-volume/?amp >>> >>> On 26 July 2022 09:16:32 Ken Bass wrote: >>> >>>> >>>> (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. >>>> >>>> TIA >>>> ken >>>> >>>> >>>> _______________________________________________ >>>> linux-lvm mailing list >>>> linux-lvm@redhat.com >>>> https://listman.redhat.com/mailman/listinfo/linux-lvm >>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ >>>> >>>> >>> _______________________________________________ >>> linux-lvm mailing list >>> linux-lvm@redhat.com >>> https://listman.redhat.com/mailman/listinfo/linux-lvm >>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ >>> >> >> _______________________________________________ >> linux-lvm mailing list >> linux-lvm@redhat.com >> https://listman.redhat.com/mailman/listinfo/linux-lvm >> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ >> > > _______________________________________________ > linux-lvm mailing list > linux-lvm@redhat.com > https://listman.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > --000000000000fe91ba05e55cf442 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

That's pretty much it. Whenever any app= attempts to read a block from the missing drive, I get the "Buffer I/= O error" message. So, even though my recovery apps can scan the LV, ma= rking blocks on the last drive as missing/unknown/etc., they can't disp= lay any recovered data - which I know does exist. Looking at raw data from = the apps' scans, I can see directory entries, as well as files. I'm= sure the inodes and bitmaps are still there for some of these, I just can&= #39;t really reverse engineer and follow them through. But isn't that w= hat the apps are supposed to do?

As for debugfs: pretty = much the same issue: in order to use it, I need to open the fs. But that (i= n debugfs) fails as well. So it can't help much. Unless I'm missing= something about debugfs.

The one thing I haven= 9;t tried is to use vgreduce to remove the missing PV; but that will also r= emove the LV as well, which is why I haven't tried it yet.

Sorry I haven't replied sooner, but it takes a long ti= me (days) to clone, then scan 16Tb...

So, please a= ny suggestions are greatly appreciated, as well as needed.

ken

(I know: No backup; got burned; = it hurts; and I will now always have backups. 'Nuf said.)

On Thu, Jul 28, 2022 at 3:12 AM Roger James <roger@beardandsandals.co.uk> wrote:=
The procedure outlined should at least get you back to a = state where the lv is consistent but with blank sectors where the data is m= issing. I would suggest using dd to make a backup partition image. Then you= can either work on that or the original to mend the fs.

On 27 July 2022 11:50:07 Roger Heflin <rogerheflin@gmail.com> w= rote:

I don't believe that is going to work.

His issue is that the filesystem is refusing to work beca= use of the
missing data.

man debugfs

It will let you manually look at the metadata and structu= res of the
ext2/3/4 fs.=C2=A0 You will likely need to use the "= -c" option.

It will be very manual and you should probably read up on= the fs
structure a bit.

A data recovery company could get most of the data back, = but they
charge 5k-10k per TB, so likely close to 100k US$.

And the issues will be that 1/3 of the metadata was on th= e missing
disk, and some of the data was on the missing disk.

I was able to do debugfs /dev/sda2 =C2=A0(my /boot) and d= o an ls and list
out the files and then do a dump <filename> /tmp/ju= nk.out and copy out
that file.

So the issue will be writing up a script to do lses and f= ind all of
the files and dump all of the files to someplace else.

On Wed, Jul 27, 2022 at 2:39 AM Roger James <roger@beardandsan= dals.co.uk> wrote:


On 26 July 2022 09:16:32 Ken Bass <daytooner@gmail.com> wrote:

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

Background: I have a very large (20TB) logical volume con= sisting 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 som= e extent, recoverable. Although, apparently the ext4 fs is not recognised.<= /div>

I activated the LV partially (via -P). But running any ut= ility on that (eg: dumpe2fs, e2fsck, ...) I get many of these =C2=A0in dmes= g:

"Buffer I/O error on dev dm-0, logical block xxxxxxx= , async page read." =C2=A0The thing is, the xxxxxxx block is on the mi= ssing 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 m= ove on. 14TB recovered is better than 0.

TIA
ken


_______________________________________________
linux-lvm mailing list
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


_______________________________________________
linux-lvm mailing list
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

_______________________________________________
linux-lvm mailing list
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.= com
https://listman.redhat.com/mailman/listinfo/lin= ux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--000000000000fe91ba05e55cf442-- --===============0709183537405220882== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://listman.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ --===============0709183537405220882==--