Sponsored Content
Top Forums UNIX for Advanced & Expert Users Corrupted journal in a Linux LVM How to recover Post 302281277 by ccj4467 on Wednesday 28th of January 2009 01:14:46 PM
Old 01-28-2009
Tried mounting as an ext2 file:

mount -t ext2 /dev/VolGroup00/LogVol00 /ramdisk/mydir

This fails with wrong fs type, bad option, bad superblock on /dev/VolGroup00/LogVol00,
missing codepage or other error.
 

5 More Discussions You Might Find Interesting

1. Linux

LVM for linux OS?

Hi, What do you means to create so OS Linux directories under LVM? So, I've installed my machine : df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 97943628 524316 92443984 1% / udev 4023852 168 4023684 1% /dev... (1 Reply)
Discussion started by: hiddenshadow
1 Replies

2. Solaris

recover a corrupted solaris10 system /usr/lib

did something very dump under /usr/lib, eg: overwite a bunch of files from a similar system's /usr/lib, while the system is live.. I have no backup on this..it crashed...and came up with a bunch of device driver load errors and hung... This is Solaris10 update 7 .. I wonder if I could do a... (0 Replies)
Discussion started by: ppchu99
0 Replies

3. Slackware

Linux on LVM

Dear all, I found, in Slackware, without using physical/raw partition Linux can be booted & OS will be in LVM but in general people use /boot from physical/raw partition to boot the RedHat linux System & root and other file systems would be in LVM. My doubt is how a system will be booted without... (5 Replies)
Discussion started by: Tlogine
5 Replies

4. UNIX for Advanced & Expert Users

How to recover the deleted file in Linux?

hi, i deleted one file from linux please let me know, if we can recover it ? if yes, pls let me know the steps to do.. (3 Replies)
Discussion started by: raghur77
3 Replies

5. Linux

Recovering corrupted LVM data: No readable superblocks

Hi all. Not sure where to post this, so figured I'd start here. I have a LVM2 partition that has become unreadable. I've scoured dozens of threads about the topic and have hit a wall, so any advice is appreciated. Below is what I think shows what my major problem is: First, a simple mount... (3 Replies)
Discussion started by: dargason
3 Replies
MKREISERFS(8)						      System Manager's Manual						     MKREISERFS(8)

NAME
mkreiserfs - create a Linux ReiserFS file system SYNOPSIS
mkreiserfs [ -dfV ] [ -b | --block-size N ] [ -h | --hash HASH ] [ -u | --uuid UUID ] [ -l | --label LABEL ] [ --format FORMAT ] [ -j | --journal-device FILE ] [ -s | --journal-size N ] [ -o | --journal-offset N ] [ -t | --transaction-max-size N ] device [ filesystem-size ] DESCRIPTION
It creates a Linux ReiserFS file system on a device (usually a disk partition). device is the special file corresponding to the device (e.g /dev/hdXX for IDE disk partition or /dev/sdXX for SCSI disk partition). filesystem-size size of filesystem in blocks. If omitted, it will be determined by mkreiserfs automatically. OPTIONS
-b | --block-size N N is block size in bytes. 4096 only for now. -h | --hash HASH HASH specifies the name of hash function file names in directories will be sorted with. Choose one of r5, rupasov, tea. r5 is default --format FORMAT FORMAT specifies a format new filsystem has to be of. Choose one of 3.5 and 3.6. If none is specified mkreiserfs will create format 3.6 if running kernel is 2.4, 3.5 if 2.2 is running, and will refuse creation under other kernels. -u | --uuid UUID Set the universally unique identifier ( UUID ) of the filesystem to UUID (see also uuidgen(8)). The format of the UUID is a series of hex digits separated by hypthens, like this: "c1b9d5a2-f162-11cf-9ece-0020afc76f16". If the option skipped, mkreiserfs generates a new one. -l | --label LABEL Set the volume label of the filesystem. LABEL can be at most 16 characters long; if it is longer than 16 characters, mkreiserfs will truncate it. -j | --journal-device FILE FILE is name of block device where the file system is to have journal on. -o | --journal-offset N N is an offset where journal starts when it is to be on a separate device. Default is 0. Makes no effect when journal is to be on a host device -s | --journal-size N N is size of journal in blocks. When journal is to be on a separate device - its size defaults to number of blocks that device has. When journal is to be on a host device - its size defaults 8193 and maximal possible value is 32749 (for blocksize 4k). Minimun is 513 for both cases. -t | --transaction-max-size N N is the maximum transaction size parameter for the journal. The default, and max possible, value is 1024 blocks. It should be less than half the size of the journal. If specifed incorrectly, it will be adjusted. -f This forces mkreiserfs to continue even if device is either whole disk, or looks mounted or is not a block device. Specified more than once allows to avoid asking for confirmation. -d This makes mkreiserfs to print debugging information during mkreiserfs. -V This prints version and exits. AUTHOR
This version of mkreiserfs has been written by Edward Shishkin <edward@namesys.com>. BUGS
No other blocksizes but 4k are available. Please, report about other bugs to the ReiserFS mail-list <reiserfs-list@namesys.com> SEE ALSO
reiserfsck(8), debugreiserfs(8), reiserfstune(8) Reiserfsprogs-3.6.4 January 2002 MKREISERFS(8)
All times are GMT -4. The time now is 10:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy