Sponsored Content
Top Forums UNIX for Advanced & Expert Users Linux EXT3 superblock recovery Post 302230037 by era on Thursday 28th of August 2008 01:34:08 PM
Old 08-28-2008
Sounds like the journal is beyond recovery, but the filesystem as such can be recovered. The journal contains stuff since the last journal sync, which is usually not a major amount of data. So there will likely be some data loss to stuff that happened just before the crash, but it might be worth doing. (Perhaps you can take a clone of the raw disk with dd so you can revert if this operation turns sour after all.)
 

9 More Discussions You Might Find Interesting

1. Linux

Help! Boot failure - corrupt superblock

Hi everyone, OK, I've made a monumental fsck-up of my linux installation AND I did not backup my data properly (idiot!), so I'm really up the proverbial without a paddle here. Basically the problem is I re-sized my /home partition (hda13) using Partition Magic 8.0, after doing so my mandrake... (0 Replies)
Discussion started by: alarmcall
0 Replies

2. Solaris

How to corrupt a superblock?

I need to corrupt a superblock of a mounted device in a soalris m/c and check recovery from an alternate superblock. How can this be done? (2 Replies)
Discussion started by: sujathan
2 Replies

3. Red Hat

superblock error

can anybody help me to recovermy superblock , the recent power crash has done some stuff on my linux redhat 9 box . when i startup the machine iam getting the following error: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it... (2 Replies)
Discussion started by: ppass
2 Replies

4. Filesystems, Disks and Memory

Linux HDD Recovery

Hello, I have my backup disks here because my server got hacked and we didn't like how liquidweb made the things. So we ask them to ship us the disk. They ran photorec and they got lots of .gz files from it. All accounts I would say. But 50% of them the .tar.gz files came corrupt. And is lefting... (2 Replies)
Discussion started by: asturmas
2 Replies

5. UNIX for Advanced & Expert Users

linux system recovery after overriding connect() by "ld.so.preload"

dear fellows; i have used ld.so.preload file to override connect() function, dynamic library overriding, it did worked really fine ...... but i went on to struck in a situation ... within the overrided connect() i have used printf once to see IP and Port to whom the connect request is being... (1 Reply)
Discussion started by: mzeeshan
1 Replies

6. Filesystems, Disks and Memory

Recovery of formatted ext3 partition

Hi! I have a really big problem right now. I (accidently) formatted a ext3 partition with "mkfs.ext3 /dev/sda1". The problem is that I REALLY need some files from there. The partition had a size of about 4GB, after accidently formatting it, I accidently rewrote Grub on it :wall: I hope I didn't... (3 Replies)
Discussion started by: al0x
3 Replies

7. Linux

CentOS Error: Superblock

Hi Guys, I really don't know where to put my query about this. And as a newbie, I think CentOS is closest to Ubuntu. Anyway, here's my dilemma. I have installed a VMWare - ESX 3.5 and installed CentOS 6 and cloned the CentOS 6. The first CentOS was working fine, when i cloned it, and the cloning... (2 Replies)
Discussion started by: init6_
2 Replies

8. UNIX for Advanced & Expert Users

Superblock marked dirty

Good morning! I met a problem on a FS with AIX 5.3 It's not possible to mount the FS because of a dirty superblock. I tried few things without success. I need your help to solve my problem guys. Do you have any idea please? Thanks a lot drp01,/home/root # mount /GSPRES/data Replaying... (9 Replies)
Discussion started by: Castelior
9 Replies

9. Red Hat

Linux bad superblock on /dev/mapper/VolGroup-lv_root

Hi Friends . my linux try to start very slowly after give it this error: mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup-lv_root, missing codepage or helper program, or other error in some cases useful info is found in syslog - try dmesg : tail or so Kernel panic... (3 Replies)
Discussion started by: blackjuan
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:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy