ext3: No journal on filesystem on dm-0


 
Thread Tools Search this Thread
Special Forums Hardware Filesystems, Disks and Memory ext3: No journal on filesystem on dm-0
# 1  
Old 10-28-2005
ext3: No journal on filesystem on dm-0

Hi Linuxers,

I am a newbie here and loggin this facilities regularly.

Recently my PC experience a power trip, my system could not boot up after restarting.

I did the following :

- Boot up with "linux rescue" using installation disk FC3
- In a shell, run "lvm vgchange --ignorelockingfailure -P -a y"
- since / parition is not mountable, I run "mknod /dev/dm-0 b 253 0"
- fsck -y /dev/dm-0, it took a long time but it clean now
- mount /dev/dm-0 /tmpRoot
- found out that there were NOTHING! except the lost+found directory which contains many files with a "#" prefix
- Restart the system but still could not boot up
One of the message says "ext3: No journal on filesystem on dm-0"

I am in a fix and what should I do now ?

Anyone could shed some light would be greatly appreciated!

regards
Chow
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Errors received while restoring my data from ext3 filesystem

Hi All, I have dual boot on my laptop - Win8 And linuxMint. From linuxmint i had copied all my data found on the NTFS partitions (on my laptop) to an external hard drive (formatted with ext3). i used rsync for this. Now after my hard disk crashed, am restoring the data back from ext3... (2 Replies)
Discussion started by: coolatt
2 Replies

2. Red Hat

Expand EXT3 filesystem ( No LVM)

hi, In my production server having Enterprise Linux Enterprise Linux Server release 5.5 (Carthage) Red Hat Enterprise Linux Server release 5.5 (Tikanga) we have a filesystem of 197 gb (Type ext 3) Hadisk in which this filesystem reside is sdb is of 217 gb. (NO LVM) Now I want to... (6 Replies)
Discussion started by: salmanraza
6 Replies

3. Linux

I need help rebuild ext3 filesystem

hi to all I wanted to edit a enigma2 image to my box .. the image is root.img .. Analysed then I have the picture and I have this: parted root.img WARNING: You are not superuser. Watch out for permissions. GNU Parted 2.2 Using /home/soft/Bureau/enigma2/root.img Welcome to GNU Parted! Type... (3 Replies)
Discussion started by: soft
3 Replies

4. Shell Programming and Scripting

How to create ext3 filesystem on regular file?

After doing something like: dd if=/dev/zero of=ext3.img bs=1024 count=1048576 I'd like to put an ext3 filesystem on ext3.img. What should I run? Thanks (2 Replies)
Discussion started by: stevenswj
2 Replies

5. UNIX for Advanced & Expert Users

Corrupted journal in a Linux LVM How to recover

Not real Linux expert but here is the problem. Shutdown this machine and then it would not reboot. From everything I can tell it looks like the journal file in the logical volume is corrupted. I have tried everything I can think of to get the volume mounted. Anybody have any ideas on how... (19 Replies)
Discussion started by: ccj4467
19 Replies

6. UNIX for Advanced & Expert Users

Enomem in Journal Retry Error

Hi, Does anyone seen this error before.. kernel: ENOMEM in journal_alloc_journal_head, retrying. I encounter this problem on IBM eServers where when the above error appears usually the machine is dead or hanged. Unless a hard reboot is been done. Is this something have to do with the memory... (1 Reply)
Discussion started by: killerserv
1 Replies

7. Filesystems, Disks and Memory

ext3 filesystem

what do you think about the ext3 journal filesystem?? (3 Replies)
Discussion started by: comadreja
3 Replies
Login or Register to Ask a Question
gfs_jadd(8)						      System Manager's Manual						       gfs_jadd(8)

NAME
gfs_jadd - Add journals to a GFS filesystem SYNOPSIS
gfs_jadd [OPTION]... <DEVICE|MOINTPOINT>... DESCRIPTION
gfs_jadd is used to add journals to a GFS filesystem after the device upon which the filesystem resides has been grown. By running gfs_jadd on a GFS filesystem, you are filling in space between the current end of the filesystem and the end of the device upon which the filesystem resides. 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 unaf- fected. gfs_jadd will not use space that has been formatted for filesystem data even if that space has never been populated with files. You may only run gfs_jadd on a mounted filesystem, addition of journals to unmounted filesystems is not supported. You only need to run gfs_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 gfs_jadd. The gfs_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. You can run gfs_jadd with the -Tv flags to get a display of the current state of a mounted GFS filesystem. This can be useful to do after the journal addition process to see if the changes have been successful. OPTIONS
-j num The number of new journals to add. This defaults to 1. -J size The size of the new journals in megabytes. The defaults to 128MB (the minimum size allowed is 32MB). If you want to add journals of different sizes to the filesystem, you'll need to run gfs_jadd once for each different size of journal. The size you specify here will be rounded down so that it is a multiple of the journal segment size which was specified at filesystem creation time. -h Help. Prints out a short usage message and exits. -q Quiet. Turns down the verbosity level. -T Test. Do all calculations, but do not write any data to the disk and do not add journals. This is used to discover what the tool would have done were it run without this flag. You probably want to turn the verbosity level up in order to gain most information from this option. -V Version. Print version information, then exit. -v Verbose. Turn up verbosity of messages. SEE ALSO
mkfs.gfs(8) gfs_grow(8) gfs_jadd(8)