search for: needs_recovery

...: 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 {Advisory Online } Value=253 Threshold= 0 Passed Id=...

Hi, I'm running 0.03b and it appears that after a clean unmount the needs_recovery flag is still set. [This makes is quite cumbersome to switch between ext2 and ext3.] How can this be fixed? Oh, and I'm very happy. - Peter -

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 with the recovered fs as root in order to get lilo(8) or grub(8)...

...ed of the sata bus so the filesystem went r/o. >>>> I would like to remove the journal but it says it can't because >>>> needs_check is set. >>> >>> What does it actually say? there is no needs_check flag AFAIK. >> >> I think he means "needs_recovery" - EXT3_FEATURE_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?): >>...

...I'm using E2fsprogs 1.37 for FS creation. And, Filesystem revision #: 1 (dynamic) There are 2 scenarios: 1. All SATA drives, RAID5 2. All PATA drives, RAID5 and wrapped in log volumes. I'm having lots of issues with fsck. I did search, but somehow not getting the right information. needs_recovery gets set on the file system, but FS state is clean. Can I safely ignore this? After the default number of mounts, it gets into auto fsck, and it takes hours to finish it. Isn't it supposed to do it quickly? Can I safely set the max mount count to zero? I appreciate if anyone tells me more o...

...;> Now this SSD dropped of the sata bus so the filesystem went r/o. >>> I would like to remove the journal but it says it can't because >>> needs_check is set. >> >> What does it actually say? there is no needs_check flag AFAIK. > > I think he means "needs_recovery" - EXT3_FEATURE_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 /d...

...e filesystem went r/o. >>>>> I would like to remove the journal but it says it can't because >>>>> needs_check is set. >>>> >>>> What does it actually say? there is no needs_check flag AFAIK. >>> >>> I think he means "needs_recovery" - EXT3_FEATURE_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...

...gt; device (an SSD). >> Now this SSD dropped of the sata bus so the filesystem went r/o. >> I would like to remove the journal but it says it can't because >> needs_check is set. > > What does it actually say? there is no needs_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 d...

.../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: 242316 First block...

...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 filetype dir_index sparse_super" Booted into rescue mode w...

...d 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 parameters, tune2fs tells me to run e2fsck first. I...

Thank you very much for the help with my problems after I changed ext2 in ext3. So far, everything is now running smootly. However, tune2fs -l /dev/hdb2 delivers among a long output one line Fls features : has_journal needs_recovery What does this mean and how can I perform such a recovery ? Thanks in advance Edgar -- ----------------------------------- Dr.-Ing. Edgar Alwers Mailto:edgaralwers@gmx.de

...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_recovery. Fortunately debugfs does. However it doesn't remove the journal uuid, or the journal device number from the superblock when I do turn of has_journal. Nor does there seem to be a debugfs command to allow this. Hence the n...

...mounted read/write. tune2fs 1.38 (30-Jun-2005) Filesystem volume name: <none> Last mounted on: /boot Filesystem UUID: ad036960-f1df-4c5e-9240-4e917527f20c Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super Default mount options: (none) Filesystem state: clean Errors behavior: Remount read-only Filesystem OS type: Linux Inode count: 55296 Block count: 439360 Reserved block count: 21968 Free blocks: 91538 Free inodes:...

...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

...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 diagnostics to find out more...

...lower (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). _________________________________________________________________...

...--- tune2fs 1.25 (20-Sep-2001) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: b1ceff3e-caca-4635-b6aa-3712b63f8917 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 1198208 Block count: 2395693 Reserved block count: 119784 Free blocks: 2315027 Free inodes: 1183124 First block:...

...er/markov02-root, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. and e2fsck says root@jessie01:~# e2fsck /dev/markov02/root e2fsck 1.42.12 (29-Aug-2014) /dev/markov02/root: recovering journal Superblock needs_recovery flag is clear, but journal has data. markov02/root is an LVM volume, built on partitions from 2 disks in a virtual machine. The initial symptom was that the VM the disks were in originally would only get as far as busybox when it started. However, I think the filesystem was OK even after that, s...

Hi, I'm about to roll out a whole bunch of Redhat Enterprise 4 workstations and have run into problems cloning from the original. Normally I would use ghost (v7.5) because it does a nice job when cloning to a different sized disk.Unfortunately it comes up with read error 29004. Looking around it seems that Symantec don't support Fedora Core 3 (with Ghost v.8 - don't know if v.9 works