From: "Marcin M. Jessa" <lists@yazzy.org>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Recovery of failed RAID 6 and LVM
Date: Sun, 25 Sep 2011 16:41:00 +0200 [thread overview]
Message-ID: <4E7F3D7C.3060705@yazzy.org> (raw)
In-Reply-To: <4E7F297C.9070403@turmel.org>
On 9/25/11 3:15 PM, Phil Turmel wrote:
> I'm sorry, Marcin, but you shouldn't expect to get your data back. Per your "mdadm -D" report, the rebuild was already 63% done, so the destruction of your data is certainly complete now.
What I don't understand is I still have the LVM info. It's just the LVs
don't have partition table stored anymore:
# pvdisplay
Logging initialised at Sun Sep 25 16:38:43 2011
Set umask from 0022 to 0077
Scanning for physical volume names
--- Physical volume ---
PV Name /dev/md0
VG Name fridge
PV Size 5.46 TiB / not usable 3.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 1430793
Free PE 102153
Allocated PE 1328640
PV UUID Ubx1OW-jCyN-Vcy2-4p2W-L6Qb-u6W8-cVkrE4
# vgdisplay
Logging initialised at Sun Sep 25 16:40:12 2011
Set umask from 0022 to 0077
Finding all volume groups
Finding volume group "fridge"
--- Volume group ---
VG Name fridge
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 33
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 7
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 5.46 TiB
PE Size 4.00 MiB
Total PE 1430793
Alloc PE / Size 1328640 / 5.07 TiB
Free PE / Size 102153 / 399.04 GiB
VG UUID ZD2fsN-dFq4-PcMB-owRh-WxGs-ciK8-PPwPbd
# lvdisplay
Logging initialised at Sun Sep 25 16:40:30 2011
Set umask from 0022 to 0077
Finding all logical volumes
--- Logical volume ---
LV Name /dev/fridge/storage
VG Name fridge
LV UUID kIhbSq-hePX-UIVv-uuiP-iK6w-djcz-iQ3cEI
LV Write Access read/write
LV Status available
# open 0
LV Size 4.88 TiB
Current LE 1280000
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 6144
Block device 253:0
--- Logical volume ---
LV Name /dev/fridge/webstorage
VG Name fridge
LV UUID PuCGo1-LkRa-doEI-n8qU-mqS3-20Cw-SICWPk
LV Write Access read/write
LV Status available
# open 0
LV Size 100.00 GiB
Current LE 25600
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 6144
Block device 253:1
--- Logical volume ---
LV Name /dev/fridge/mailstorage
VG Name fridge
LV UUID 538TGs-fRYt-VT1n-r8jE-Uvv3-nNXl-Cf8ojP
LV Write Access read/write
LV Status available
# open 0
LV Size 30.00 GiB
Current LE 7680
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 6144
Block device 253:2
--- Logical volume ---
LV Name /dev/fridge/web01
VG Name fridge
LV UUID NsABmI-ok5I-GCaE-yGV6-Dqp6-Qedz-jVDS6Y
LV Write Access read/write
LV Status available
# open 0
LV Size 10.00 GiB
Current LE 2560
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 6144
Block device 253:3
--- Logical volume ---
LV Name /dev/fridge/db01
VG Name fridge
LV UUID qa88nB-MqX8-25YN-MEqf-ln81-vNtP-w2yVMW
LV Write Access read/write
LV Status available
# open 0
LV Size 10.00 GiB
Current LE 2560
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 6144
Block device 253:4
--- Logical volume ---
LV Name /dev/fridge/mail01
VG Name fridge
LV UUID qxUbLd-SaDq-wCwd-Z5M6-2llk-8SJh-vTlruR
LV Write Access read/write
LV Status available
# open 0
LV Size 10.00 GiB
Current LE 2560
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 6144
Block device 253:5
--- Logical volume ---
LV Name /dev/fridge/win8
VG Name fridge
LV UUID TPsBeN-Nj2o-w1mt-pkS8-d9zu-wCMm-vRv3e7
LV Write Access read/write
LV Status available
# open 0
LV Size 30.00 GiB
Current LE 7680
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 6144
Block device 253:6
--
Marcin M. Jessa
next prev parent reply other threads:[~2011-09-25 14:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 7:55 Recovery of failed RAID 6 and LVM Marcin M. Jessa
2011-09-25 8:39 ` Stan Hoeppner
2011-09-25 10:07 ` Marcin M. Jessa
2011-09-25 13:15 ` Phil Turmel
2011-09-25 14:16 ` Marcin M. Jessa
2011-09-25 16:43 ` Phil Turmel
2011-09-25 14:41 ` Marcin M. Jessa [this message]
2011-09-25 16:19 ` Phil Turmel
2011-09-25 21:40 ` NeilBrown
2011-09-25 21:58 ` Marcin M. Jessa
2011-09-25 22:18 ` NeilBrown
2011-09-25 22:21 ` Marcin M. Jessa
[not found] ` <4E804062.3020700@yazzy.org>
2011-09-26 9:31 ` NeilBrown
2011-09-26 10:53 ` Marcin M. Jessa
2011-09-26 11:10 ` NeilBrown
2011-09-27 19:12 ` Marcin M. Jessa
2011-09-27 23:13 ` NeilBrown
2011-09-28 2:50 ` Stan Hoeppner
2011-09-28 7:10 ` Marcin M. Jessa
2011-09-28 7:51 ` David Brown
2011-09-28 16:12 ` Stan Hoeppner
2011-09-28 16:30 ` Marcin M. Jessa
2011-09-28 18:56 ` Thomas Fjellstrom
2011-09-28 19:26 ` Marcin M. Jessa
2011-09-28 19:42 ` Thomas Fjellstrom
2011-09-28 23:49 ` NeilBrown
2011-09-29 9:03 ` David Brown
2011-09-29 15:21 ` Stan Hoeppner
2011-09-29 17:14 ` David Brown
2011-09-29 18:28 ` Dan Williams
2011-09-29 23:07 ` NeilBrown
2011-09-30 0:18 ` Williams, Dan J
2011-10-05 2:15 ` NeilBrown
2011-09-28 10:38 ` Michal Soltys
2011-09-28 13:20 ` Brad Campbell
2011-09-28 19:02 ` Thomas Fjellstrom
2011-09-28 16:31 ` Stan Hoeppner
2011-09-28 16:37 ` Marcin M. Jessa
2011-09-28 19:03 ` Thomas Fjellstrom
2011-09-28 19:29 ` Marcin M. Jessa
2011-09-28 19:43 ` Thomas Fjellstrom
2011-09-30 20:01 ` Marcin M. Jessa
2011-09-30 21:47 ` Thomas Fjellstrom
2011-09-30 22:30 ` Marcin M. Jessa
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=4E7F3D7C.3060705@yazzy.org \
--to=lists@yazzy.org \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.