7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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. Red Hat
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
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:
WARNING: You are not superuser. Watch out for permissions.
GNU Parted 2.2
Welcome to GNU Parted! Type... (3 Replies)
Discussion started by: soft
4. Shell Programming and Scripting
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
5. UNIX for Advanced & Expert Users
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
6. UNIX for Advanced & Expert Users
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
7. Filesystems, Disks and Memory
what do you think about the ext3 journal filesystem?? (3 Replies)
Discussion started by: comadreja
E2UNDO(8) System Manager's Manual E2UNDO(8)
e2undo - Replay an undo log for an ext2/ext3/ext4 filesystem
e2undo [ -f ] [ -h ] [ -n ] [ -o offset ] [ -v ] [ -z undo_file ] undo_log device
e2undo will replay the undo log undo_log for an ext2/ext3/ext4 filesystem found on device. This can be used to undo a failed operation by
an e2fsprogs program.
-f Normally, e2undo will check the filesystem superblock to make sure the undo log matches with the filesystem on the device. If they
do not match, e2undo will refuse to apply the undo log as a safety mechanism. The -f option disables this safety mechanism.
-h Display a usage message.
-n Dry-run; do not actually write blocks back to the filesystem.
Specify the filesystem's offset (in bytes) from the beginning of the device or file.
-v Report which block we're currently replaying.
Before overwriting a file system block, write the old contents of the block to an undo file. This undo file can be used with
e2undo(8) to restore the old contents of the file system should something go wrong. If the empty string is passed as the undo_file
argument, the undo file will be written to a file named e2undo-device.e2undo in the directory specified via the E2FSPROGS_UNDO_DIR
WARNING: The undo file cannot be used to recover from a power or system crash.
e2undo was written by Aneesh Kumar K.V. (firstname.lastname@example.org)
e2undo is part of the e2fsprogs package and is available from http://e2fsprogs.sourceforge.net.
E2fsprogs version 1.44.1 March 2018 E2UNDO(8)