search for: has_journ

...erblock as on the main device. Normally it fails to find a superblock on the journal device. - e2fsck will not progress if the journal device is bad (e.g. when the super block is wrong as above). I cannot say 'Ignore the journal and fsck'. It just stops. Even after I turn off has_journal (see below), it still won't let me fsck because there is a uuid and a journal device set in the superblock. I now have a hacked e2fsck which ignores the journal. - tune2fs doesn't let me turn off has_journal if needs_recovery is set, and doesn't let me turn off needs_re...

Hi all, I'm trying to resize a journal on my root filesystem. This is Ext3, kernel 2.4.19, latest e2fsprogs + htree patch. I've remounted my root filesystem as ext2, but still when I 'tune2fs -O ^has_journal' I get ---- The has_journal flag may only be cleared when the filesystem is unmounted or mounted read-only. ---- So, how can I increase the size of the journal? I can't remount the root filesystem as readonly because I don't have console access (I only have SSH access, because the...

...ing to use the e2fs progs package. Origianlly I used version 1.38, but after experiencing segfaults in e2fsck -which now is solved, I upgraded to 1.39, but now I have hit another problem (on another partition): The partition was formatted as ext3, and debugfs / dumpfs showed that the feature 'has_journal' was present (as expected). The e2fsck command gave the following: # e2fsck -B4096 -b32768 /dev/hda11 e2fsck 1.39 (29-May-2006) e2fsck: Attempt to read block from filesystem resulted in short read while checking ext3 journal for /var So it seemed like a problem in the journal, as I could n...

....32 (09-Nov-2002) e2fsck 1.32 (09-Nov-2002) fsck.ext2: Attempt to read block from filesystem resulted in short read while checking ext3 journal for /backup I thought removing the journal might help. I doubt that the files that interest me were open at the time. [root at marvin root]# tune2fs -O ^has_journal /dev/hdb1 tune2fs 1.32 (09-Nov-2002) The needs_recovery flag is set. Please run e2fsck before clearing the has_journal flag. Any ideas? Thanks! Tom [root at marvin download]# ide-smart /dev/hdb1 Id= 3 Status=39 {Prefailure Online } Value=219 Threshold= 63 Passed Id= 4 Status=50 {A...

...journal device with the -j option) and this gives me "External journal has bad superblock" which is also understandable since the journal device was also corrupted. Next, I tried to clear the journal parameter in hope of being able to run fsck after that is done. But "tune2fs -O ^ has_journal" tells me "The needs_recovery flag is set. Please run e2fsck before clearing the has_journal flag." And of course, I can't reset the "needs_recovery" flag either. So now e2fsck is telling me that the journal is corrupted and if I try to clear the journal parameter...

...on embedded I have e2fsprogs-1.27-1. On the 2.6 desktop it's e2fsprogs-1.35-12. I built e2fsprogs-1.38 for the desktop and the result was the same. I used dumpe2fs on the working and non-working filesystems and found that the newer FS has different features: < Filesystem features: has_journal filetype sparse_super > Filesystem features: has_journal resize_inode filetype sparse_super After writing to a new FS on the desktop a further feature is added, < Filesystem features: has_journal resize_inode filetype sparse_super > Filesystem features: has_journal ext...

...and "tune2fs -l /dev/sda5" and > toggle features too (read the man page). It's most likely the > dir_index feature... > Thanks Peter for the prod in the right direction. A v4 filesystem shows these features # tune2fs -l /dev/sda1 | grep features Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file A v3 filesystem has these features # tune2fs -l /dev/sda5 | grep features Filesystem features: has_journal filetype needs_recovery sparse_super Tunes2fs from v4.2 can be used to remove "has_journal filety...

After a (hardware) crash yesterday, I was unable to boot up due to unrecoverable ide errors (according to the printk()s) when accessing the root filesystem's journal for recovery. Unable to recover, I tried deleting the has_journal option, but that was disallowed given that the needs_recovery flag was set. I saw no way to unset that flag. Unable to access the backups (they were on a fw drive), I was able to dump the unrecovered filesystem, mke2fs and restore. (And then had to dl a new rescue floppy so that I could boot w...

...convert a lustre FS using external journals to one with async journals enabled. Question is whether the procedure: umount <filesystem> on all clients umount <osts> on all OSSes e2fsck <ost-device> on all OSSes for all all OSTs tune2fs -O ^has_journal <ost-device> on all OSSes for all all OSTs lctl set_param obdfilter.*.sync_journal=0 on all OSSes mount <osts> on all OSSes mount <filesystem> on all clients is correct to do the job? (I hope it isn''t neccessary to recreate a FS from sc...

...r/o with no journal updates pending, this will be compatible. I'm trying to also cover the case where something goes wrong during the subsequent install and we reboot into a system without ext3 support but where the root file system did not get unmounted properly first. Using tune2fs -O ^has_journal /dev/xxx on a r/o ext3 root appears to succeed but I later see file system corruption after remounting r/w to install the non-ext2 system files and suspect that the kernel still has it fingers on some old journal resources after the r/w remount following removal of the journal. Mike Accetta La...

...ste:# tune2fs -l /dev/hdb2 tune2fs 1.27 (8-Mar-2002) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: 60ae4fae-f11b-4156-ade8-1aa1b63d3bc5 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super Filesystem state: clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 262144 Block count: 524112 Reserved block count: 26205 Free blocks: 185025 Free inodes:...

...ebugfs 1.28 (31-Aug-2002) /dev/hda1: Can't read an inode bitmap while reading inode bitmap debugfs: open -c /dev/hda1 /dev/hda1: catastrophic mode - not reading inode or group bitmaps debugfs: stat <8> stat: Invalid argument while reading inode 8 debugfs: stats ... Filesystem features: has_journal filetype sparse_super Filesystem state: clean with errors ... Directories: 1122431 Group 0: block bitmap at 33188, inode bitmap at 19132, inode table at 1027802808 6794 free blocks, 15870 free inodes, 1720 used directories Group 1: block bitmap at 0, inode bitmap...

When I first installed ext3, it worked as expected. After a crash, journals would be played, and no fsck. Now, every crash causes an fsck, just like it were a regular ext2, even though / has a journal and is being mounted as ext3. Some fs info for / Filesystem features: has_journal filetype sparse_super Filesystem state: not clean Errors behavior: Continue Some fs info for /home, which seems to be working OK: Filesystem features: has_journal filetype needs_recovery sparse_super Filesystem state: clean Errors behavior: Continue Maybe...

...ds_check flag AFAIK. I think he means "needs_recovery" - EXT3_FEATURE_INCOMPAT_RECOVER set when journal recovery is needed after an unclean shutdown. What you want is to run (per the tune2fs(8) man page, maybe something should go into the e2fsck(8) man page as well?): tune2fs -f -O ^has_journal /dev/XXX e2fsck -fp /dev/XXX tune2fs -J device=/dev/YYY /dev/XXX This will remove the journal from the filesystem, run e2fsck to fix whatever problems it finds, then re-add the journal device (if you have one, otherwise just use "tune2fs -j" to add an internal journal). Note tha...

...TURE_INCOMPAT_RECOVER >> set when journal recovery is needed after an unclean shutdown. > > Yes, that's the one. > >> What you want is to run (per the tune2fs(8) man page, maybe something >> should go into the e2fsck(8) man page as well?): >> tune2fs -f -O ^has_journal /dev/XXX > > That one was denied because of the needs_recovery. Even with the "-f" ? Hum, that sounds like it might be a bug then. What version? -Eric

...e2fsck 1.32 (09-Nov-2002) e2fsck: Invalid argument while checking ext3 journal for /dev/md0 ------------------------------------------------------------------------------ And once again got this error wrt the journal. Note that before I even tried this -S procedure, I tried to simply turn off the has_journal bit using tune2fs: didn't help. (I'm willing to lose the info in the journal, as long as I can get the rest of my large f/s.) But tune2fs and friends gave me a chicken-and-egg error about the invalid arg wrt the journal, while trying to turn it off (duhh). At this point I've begun...

...ust few files.. Is there any way, any tool that would allow to recover the data? Probably there is some specific options for the recovery ralated with journaling in ext3? I have used debugfs, it produced following, if it helps: debugfs: open -f -w /dev/sdb1 debugfs: features Filesystem features: has_journal resize_inode filetype needs_recovery sparse_super large_file thanks, Dmitry

...18.7smp and RAID 5. Also tune2fs 1.27 (8-Mar-2002) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: 80307f32-6acd-4856-8ce4-63044f30d057 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super large_file Filesystem state: clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 122109952 Block count: 244197920 Reserved block count: 12209896 [....] Can I run any other dia...

Greetings, I recently cpio-ed some user directories onto a new ext3 partion. After putting this file server's partition into production, I noticed a .journal file in the root directory of the partition dated well before the creation of this partition. I think this .journal file was copied over from the old filesystem and I am concerned that I over-wrote this current filesystem's

...iles grows, my application gets slower and slower (the app is works something like a cache for another app and I can't redesign the way it distributes files into disk due to the other app requirements). The filesystem I use is ext3 with teh following options enabled: Filesystem features: has_journal resize_inode dir_index filetype needs_recovery sparse_super large_file Is there any way to improve performance in ext3? Would you suggest another FS for this situation (this is a prodution server, so I need a stable one) ? Thanks in advance (and please excuse my bad english). ________________...