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
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
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
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
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
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
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
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
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
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
LEARN ABOUT CENTOS
gfs2_jadd
gfs2_jadd(8) System Manager's Manual gfs2_jadd(8)
NAME
gfs2_jadd - Add journals to a GFS2 filesystem
SYNOPSIS
gfs2_jadd [OPTION]... <DEVICE|MOINTPOINT>...
DESCRIPTION
gfs2_jadd is used to add journals (and a few other per-node files) to a GFS2 filesystem. When this operation is complete, the journal
index is updated so that machines mounting the filesystem at a later date will see the newly created journals in addition to the journals
already there. Machines which are already running in the cluster are unaffected.
You may only run gfs2_jadd on a mounted filesystem, addition of journals to unmounted filesystems is not supported. You only need to run
gfs2_jadd on one node in the cluster. All the other nodes will see the expansion has occurred when required.
You must be superuser to execute gfs2_jadd. The gfs2_jadd tool tries to prevent you from corrupting your filesystem by checking as many of
the likely problems as it can. When growing a filesystem, only the last step of updating the journal index affects the currently mounted
filesystem and so failure part way through the expansion process should leave your filesystem in its original state.
OPTIONS
-c MegaBytes
Initial size of each journal's quota change file
-D Print out debugging information about the filesystem layout.
-h Prints out a short usage message and exits.
-J size
The size of the new journals in megabytes. The defaults to 32MB (the minimum size allowed is 8MB). If you want to add journals of
different sizes to the filesystem, you'll need to run gfs2_jadd once for each different size of journal.
-j num The number of new journals to add.
-q Be quiet. Don't print anything.
-V Version. Print version information, then exit.
SEE ALSO
mkfs.gfs2(8) gfs2_grow(8)
gfs2_jadd(8)