From: "Ralf Zerres" <rzerres@networkx.de>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Desater Recovery <urgent>
Date: Mon Apr 22 10:14:02 2002 [thread overview]
Message-ID: <002401c1ea10$873d91a0$6b01a8c0@PC07> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 5853 bytes --]
hello everybody,
on a production system we do have a serious data destruction problem.
Any help leading us to restore the filesystem will be honored. We can dicuss financial details later.
First I'd like to describe the situation giving you a picture wether it is possible to restore the data.
Please answer as soon as possible to give me a hint wether I should wait for a detailed analysis,
if it make sense to dig deeper or if it is more likely that people have to reinsert the data from printed
information.
0. PROBLEM:
=========
Destructed Filesystem after resizing LVG running a Postgres Database.
###
# There is no actual backup, which is the mad point!!!!
###
24 days of DATA updates are lost right now!
I. Environment
===========
System: Dual Prozessor PIII (2 CPU's 1Mhz)
OS: Linux 2.4.9
Harddisk: SCSI-3 (as Raid-5)
Controller: GDT
LVM version: 1.0.1-rc2(30/08/2001)
Kernel sees one harddrive (/dev/scsi/host2/bus0/target0)
Root is on standard ext3 fs (partition 5)
LVM has a Physical Volumegroup (KI) on partition 7
The system runs a PostgreSQL Database (version 7.1.3). The Data-Structures live on a Logical-Volume-Group
which was mounted as /var/lib/postgres as a ext3 filesystem.
Everything was working until 4 hours ago, before LVG was resized.
II. Changes
The LVG /dev/ki/postgres was reduced from 8 GB to 800MB. Before we did that a df has shown a used size
of 366 MB data.
Postgres was shut down. No other process was writing to /dev/ki/postgres.
# e2fsadm --size - 4,5G
Worked out, but remounting has shown incorrect structure.
A new LVG was created
# lvcreate --size 2,5G --name opt /dev/ki/opt
Here the dump-information from the actual Volume-Group after resizing was successful.
----------------------------------------------schnipp / schnapp ------------------------------------------------
#vgdisplay -v /dev/ki
--- Volume group ---
VG Name ki
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 256
Cur LV 7
Open LV 6
MAX LV Size 255.99 GB
Max PV 256
Cur PV 1
Act PV 1
VG Size 48.77 GB
PE Size 4 MB
Total PE 12484
Alloc PE / Size 11968 / 46.75 GB
Free PE / Size 516 / 2.02 GB
VG UUID P6LodN-bQUg-u5WF-03Cu-A22a-UUhE-NsKhvZ
--- Logical volume ---
LV Name /dev/ki/export
VG Name ki
LV Write Access read/write
LV Status available
LV # 1
# open 1
LV Size 6 GB
Current LE 1536
Allocated LE 1536
Allocation next free
Read ahead sectors 120
Block device 58:0
--- Logical volume ---
LV Name /dev/ki/var
VG Name ki
LV Write Access read/write
LV Status available
LV # 2
# open 1
LV Size 1 GB
Current LE 256
Allocated LE 256
Allocation next free
Read ahead sectors 120
Block device 58:1
--- Logical volume ---
LV Name /dev/ki/tmp
VG Name ki
LV Write Access read/write
LV Status available
LV # 3
# open 1
LV Size 1 GB
Current LE 256
Allocated LE 256
Allocation next free
Read ahead sectors 120
Block device 58:2
--- Logical volume ---
LV Name /dev/ki/home
VG Name ki
LV Write Access read/write
LV Status available
LV # 4
# open 1
LV Size 30 GB
Current LE 7680
Allocated LE 7680
Allocation next free
Read ahead sectors 120
Block device 58:3
--- Logical volume ---
LV Name /dev/ki/postgres
VG Name ki
LV Write Access read/write
LV Status available
LV # 5
# open 0
LV Size 3.78 GB
Current LE 968
Allocated LE 968
Allocation next free
Read ahead sectors 120
Block device 58:4
--- Logical volume ---
LV Name /dev/ki/www
VG Name ki
LV Write Access read/write
LV Status available
LV # 6
# open 1
LV Size 2.44 GB
Current LE 625
Allocated LE 625
Allocation next free
Read ahead sectors 120
Block device 58:5
--- Logical volume ---
LV Name /dev/ki/opt
VG Name ki
LV Write Access read/write
LV Status available
LV # 7
# open 1
LV Size 2.53 GB
Current LE 647
Allocated LE 647
Allocation next free
Read ahead sectors 120
Block device 58:6
--- Physical volumes ---
PV Name (#) /dev/scsi/host2/bus0/target0/lun0/part7 (1)
PV Status available / allocatable
Total PE / Free PE 12484 / 516
Volume-Group: KI
----------------------------------------------schnipp / schnapp ------------------------------------------------
The sysadmin was running a vgscan an lvscan. Afterwards he runs
# e2fsck -y -f /dev/ki/postgres
now the mount on /var/lib/postgres was successful, but all date were gone!
I found a long list of dir-entries in the lost+found subdir. No file-entries.
What can we do?
Ralf
[-- Attachment #1.2: Type: text/html, Size: 16963 bytes --]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Ralf, Zerres.vcf --]
[-- Type: text/x-vcard; name="Ralf, Zerres.vcf", Size: 324 bytes --]
BEGIN:VCARD
VERSION:2.1
N:Ralf;Zerres
FN:Ralf, Zerres
ORG:Networkx GmbH
TEL;WORK;VOICE:+49 221 937725 - 0
TEL;WORK;FAX:+49 221 937725 - 18
ADR;WORK:;;Marktstr. 8;Köln;;50968
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Marktstr. 8=0D=0AK=F6ln 50968
EMAIL;PREF;INTERNET:rzerres@networkx.de
REV:20020422T151525Z
END:VCARD
next reply other threads:[~2002-04-22 10:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 10:14 Ralf Zerres [this message]
2002-04-22 12:05 ` [linux-lvm] Desater Recovery <urgent> Joe Thornber
2002-04-22 12:13 ` Ralf Zerres
2002-04-22 12:22 ` Joe Thornber
2002-04-22 12:32 ` Andreas Dilger
2002-04-23 1:43 ` Bas
2002-04-25 4:00 ` Heinz J . Mauelshagen
2002-04-22 12:25 ` Andreas Dilger
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='002401c1ea10$873d91a0$6b01a8c0@PC07' \
--to=rzerres@networkx.de \
--cc=linux-lvm@sistina.com \
/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.