10-09-2008
Quote:
Originally Posted by
otheus
Ouch!
Have you done ANYTHING to md0 or the underlying devices since then??
No, I haven't done anything to it.
Quote:
I believe that md0 uses an on-disk block for tracking meta information, but that essentially, the underlying partitions are simply kept in sync as normal filesystems are. Translation: you can directly mount the underlying file system. If they're not too out-of-sync, you can just fsck and mount. If the fsck fails at first because the md0 blasted it (unlikely), you can just use a backup superblock and specify that to fsck.
But how exactly do I mount lvm volumes without them being in a group? Does mounting do anything to the underlying devices as you ask?
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hey peeps,
Here is somethin u might find interestin....
Is it possible to recover data from a partition which used to be an ext3 file sytem with some nice forgotten backups, which now is an lvm partion containg root partition of another OS. :)
I couldn't create any mess better than this, can... (2 Replies)
Discussion started by: squid04
2 Replies
2. AIX
Hi all,
I am still working on my mksysb restore.
My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored.
0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any
available boot images. Please correct this... (0 Replies)
Discussion started by: pobman
0 Replies
3. HP-UX
Hi,
I'm new to HP-UX.
I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3
Thanks (4 Replies)
Discussion started by: lamoul
4 Replies
4. UNIX for Dummies Questions & Answers
Hi Guys,
I m using redhat 6, I have installed root partition as non-LVM .
Is there any way i can convert it to LVM? (1 Reply)
Discussion started by: pinga123
1 Replies
5. Filesystems, Disks and Memory
Hi
I am new on your forum, because I need some help.
I have a server with debian and proxmox 2.
The HardDisk is broken.
I am in rescue mode, and I can't mount LVM partition to recover my backups.
What I've already done :
# fdisk -l
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255... (0 Replies)
Discussion started by: pppplu
0 Replies
6. UNIX for Advanced & Expert Users
Hi guys,
I would like to ask your opinion about my theory, how to fix my broken LVM without risking any data loss.
I use Archlinux at home. I just love this distro, even it gives me a lots of work (particularly after system updates).
Basic system spec:
AMD FX(tm)-6100 Six-Core Processor... (1 Reply)
Discussion started by: lyynxxx
1 Replies
7. Linux
Hi all,
I been trying to recover a volume group of single PV.
vgcfgrestore output
# vgcfgrestore vgoraData
Couldn't find device with uuid 'a3onP5-RdbR-fdgq-sDkS-ZtFs-83Q5-kFJj43'.
Cannot restore Volume Group vgoraData with 1 PVs marked as missing.
Restore failed.
fdisk output
... (1 Reply)
Discussion started by: h@foorsa.biz
1 Replies
lofi(7D) Devices lofi(7D)
NAME
lofi - Loopback file driver
DESCRIPTION
The lofi file driver exports a file as a block device. Reads and writes to the block device are translated to reads and writes on the
underlying file. This is useful when the file contains a file system image. Exporting it as a block device through the lofi file driver
allows normal system utilities to operate on the image through the block device (like fstyp(1M)fsck(1M), and mount(1M). This is useful for
accessing CD-ROM and FAT floppy images. See lofiadm(1M) for examples.
File block device entries are contained in /dev/lofi, while /dev/rlofi contains the character (or raw) device entries. Entries are in the
form of decimal numbers which are assigned through lofiadm(1M). When created, these device entries are owned by root, in group sys, and
have permissions 0600. While ownership, group, and permission settings can be altered, there are possible ramifications. See lofiadm(1M)
for more information.
FILES
/dev/lofictl
Master control device
/dev/lofi/n
Block device for file n
/dev/rlofi/n
Character device for file n
/kernel/drv/lofi
32-bit driver
/kernel/drv/lofi.conf
Driver configuration file. (Should not be altered.)
/kernel/drv/sparcv9/lofi
64-bit driver
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsr, SUNWcarx.u |
+-----------------------------+-----------------------------+
SEE ALSO
lofiadm(1M), fsck(1M), fstyp(1M), mount(1M), newfs(1M), attributes(5), lofs(7FS)
NOTES
Just as you would not directly access a disk device that has mounted file systems, you should not access a file associated with a block
device except through the lofi file driver.
For compatability purposes, a raw device is also exported along with the block device. For example, newfs(1M) requires one.
SunOS 5.10 30 Jul 1999 lofi(7D)