[Bugme-new] [Bug 404] New: turning off htree causes fsck to complain
bugme-daemon at smtp.osdl.org
bugme-daemon at smtp.osdl.org
Mon Feb 24 11:42:29 PST 2003
http://bugme.osdl.org/show_bug.cgi?id=404
Summary: turning off htree causes fsck to complain
Kernel Version: 2.5.62-bk7
Status: NEW
Severity: low
Owner: akpm at digeo.com
Submitter: bwindle-kbt at fint.org
Distribution: Debian Testing
Hardware Environment: x86, IDE
Software Environment:
ext3+htree
Problem Description:
It seems that if you remove htree (tune2fs -O ^dir_index /dev/xxx), and do a
fsck, it will complain about inodes with INDEX_FL flag set on filesystem
without htree support. This isn't a big deal, but causes auto-fscks-on-boot to
fail, and drop you to single-user mode, scaring the living crap out of the
SysAdmin in the process. I don't know if tune2fs should remove the INDEX_FL
flag when removing htree from an ext3 drive, or if the kernel can fix these
(very minor) "errors". Or should I be complaining to the author of tune2fs?
Steps to reproduce:
Create/modify an ext3 partition with htree, force a directory optimization with
e2fsck -D /dev/xxx, then remove htree, and fsck again. You'll get lots of these:
Inode 1999038 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index<y>? yes
Inode 2015948 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index<y>? yes
Inode 2033401 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index<y>? yes
Inode 2051968 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index<y>? yes
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the Bugme-new
mailing list