search for: e2fstools

Displaying 4 results from an estimated 4 matches for "e2fstools".

2001 Sep 19
1
Why is .journal file sometimes visible and sometimes not?
Hi. I recently migrated two machines from ext2 to ext3. Kernels (nearly identical) are 2.4.9-ac9 + preemptivity-patch + wrr-patch. The Installations are based on Mandrake 7.2 + 8.0. Also I have e2fstools-1.23 newly compiled on them. Both machines have two ext3 partitions (root + multimedia-data). On one machine I see a .journal file on both partitions, on the other machine (Mandrake-8.0) it's only visible on the root-partition. Journalling works flawlessly and 'cat /proc/mounts' sho...
2001 Feb 19
1
Dead puppies (and Linux boxen) aren't much fun.
Fellow riders of the bleeding edge of ext3 technology, I've been playing with ext3 on my workstation. For the most part it has worked very well, but right now I have a non-functional system. I've got patches out the wazoo on this kernel - 2.2.18 + Alan's 2.2.19pre13 + ext3-0.0.6a + i2c-2.5.5 + lm_sensors-2.5.5 + udf-0.9.3. Here is the output I get: EXT3-fs: WARNING: recovery
2002 Dec 04
0
[Fwd: [RESEND] 2.4.20: ext3: Assertion failure in journal_forget()/Oops on another system]
...Block = 573552, count = 14 Dec 1 22:17:55 pollux kernel: Assertion failure in journal_forget() at transaction.c:1225: "!jh->b_committed_data" Trying to access the partition resulted in processes hanging in D state: 5336 pts/0 D 0:00 ls -a -N --color=tty -T 0 -l /mnt/data8 e2fstools version is 1.32 and the partition was created with this version using 'mke2fs -j -b 2048 -i 4096 -R stride=16 /dev/md11'. An earlier dump of the partition data using tune2fs -l gave: tune2fs 1.32 (09-Nov-2002) Filesystem volume name: <none> Last mounted on: <not availa...
2005 Jun 14
1
bad inode number followed by ext3_abort and remount readonly
...ich the machine is operational again. This particular example is a SATA disk, but it has happened to a regular old IDE disk as well. It is always the root partition. The bad inode number varies (but is always either 3 or 9). There are no other errors about the disk in the log. Kernel: 2.6.11.7 e2fstools: 1.35 (28-Feb-2004) Any thoughts on how to proceed here? Unfortunately, I'm not able to duplicate this at will. David