search for: needs_recovery

Displaying 20 results from an estimated 67 matches for "needs_recovery".

2000 Nov 16
4
needs_recovery flag
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 -
2005 Apr 09
6
short read while checking ext3 journal
...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@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@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...
2005 Oct 19
2
EXT3 journalling issue
...9;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 m...
2002 Apr 14
5
Problems with ext3
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
2002 Aug 20
8
unmountable ext3 root recovery
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)...
2004 Sep 24
2
Corrupted journal
...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 firs...
2006 Jan 26
1
Ext3 filesystem access after downgrade from v4.2 to v3.6 [SOLVED]
...(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 rescu...
2002 Dec 04
6
ext3-Partition lost after crash !?
...;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...
2001 Dec 11
4
More external journal woes.
...;'. 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. H...
2005 Nov 24
4
Assertion failure in ext3_sync_file() at fs/ext3/fsync.c:50: "ext3_journal_current_handle() == 0"
...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:...
2006 Jul 26
7
data recovering in EXT3
...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
2002 May 13
11
Assertion failure in do_get_write_access() at transaction.c:609:
Hi all (and developers in particular) I just got bitten by this Assertion. The one that starts as in the subject, and ends with: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)" Google reminds me that it was mentioned a few times earlier this year, but I couldn''t find any statement saying that it has been fixed. I got this in a 2.4.16 kernel, though the
2003 Sep 18
3
Freeing blocks not in datazone
...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...
2001 Nov 19
3
df report
...--- 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:...
2005 Jun 08
3
clone RHEL 4 ext3 partition
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
2003 Aug 18
20
another seriously corrupt ext3 -- pesky journal
Hi Ted and all, I have a couple of questions near the end of this message, but first I have to describe my problem in some detail. The power failure on Thursday did something evil to my ext3 file system (box running RH9+patches, ext3, /dev/md0, raid5 driver, 400GB f/s using 3x200GB IDE drives and one hot-spare). The f/s got corrupt badly and the symptoms are very similar to what
2006 Feb 23
1
Ext3: Ordered : Fsync question
Does Fsync of a file on a ext3 fs mounted with "ordered" option(the default) result in flush the dirty data buffers in the fs that correspond to previous transactions. In other words, if I keep writing to file1 (lots of data), log something to file2, keep fsyncing file2 after every write - does this mean file1 data would be committed by fsyncs on file2. Please copy me on your replies
2005 Apr 20
2
(no subject)
...ved from RHEL3 to RHEL4. I had to install from c0d0p6 so partition could not be reformated during install. Thanks, Mindaugas # dumpe2fs /dev/cciss/c0d0p1 | fgrep features dumpe2fs 1.35 (28-Feb-2004) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super # dumpe2fs /dev/cciss/c0d0p6 | fgrep features dumpe2fs 1.35 (28-Feb-2004) Filesystem features: has_journal filetype needs_recovery sparse_super large_file
2000 Dec 05
15
State of the union
The list has gotten pretty quiet over the last week. As I understand it, we are down to the following big ticket items: 1. Quotas on meta journaling 2. ext3 + LFS 3. Various minor bugs. Is this accurate? -- Keith Barrett Red Hat HA Team
2003 Jan 19
3
All data "gone," lost+found is left.
...fs 1.32 (09-Nov-2002) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: 1c762a60-0820-4ad1-9e61-ea5066870851 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal dir_index filetype needs_recovery sparse_super Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 3751936 Block count: 7502347 Reserved block count: 375117 Free blocks: 7376401 Free inodes:...