File System Issues during bootup

Phoe6 orsenthil at
Mon Feb 21 11:20:34 PST 2005

Jeremy Utley <jeremy at> wrote:
> Gerard Beekmans wrote:
> >
> >Senthill, if you can provide output of that same command (tune2fs
> >-l /dev/hda4) when you run it from Fedora Core 3, then we can compare it and
> >offer some suggestions to you that you might try out.
> >
> I happened to have an ext3 filesystem created by FC3 here.  Here's the
> features line from me running tune2fs -l:
> Filesystem features:      has_journal ext_attr resize_inode dir_index
> filetype sparse_super large_file

Gerard, here is my output of command: tune2fs -l /dev/hda4 

tune2fs 1.35 (28-Feb-2004)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          30bcdd9e-5639-4dae-9497-07a5d40478e1
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      ext_attr resize_inode filetype sparse_super large_file
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              999424
Block count:              1996076
Reserved block count:     99803
Free blocks:              1350450
Free inodes:              861874
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16384
Inode blocks per group:   512
Filesystem created:       Sat Feb 19 01:36:42 2005
Last mount time:          Tue Feb 22 00:24:22 2005
Last write time:          Tue Feb 22 00:24:22 2005
Mount count:              2
Maximum mount count:      21
Last checked:             Sat Feb 19 01:38:23 2005
Check interval:           15552000 (6 months)
Next check after:         Thu Aug 18 01:38:23 2005
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:		  128
Default directory hash:   tea
Directory Hash Seed:      e3c60762-4e74-4492-b519-bec0aaf344a4

There are few things discussed in this thread:
1) e2fsprogs out, version 1.36 on lfs system ( let me try and give you
the results)

I rebuilt a copy of e2fsprogs on my host system, in my home dir, and
reformatted the partitions with it. I rebooted, and it worked just fine.
But. will not reformatting my /mnt/hda4 spoil my lfs completely? ( The
poster in the thread did not give the exact details of what he did)

3) If I have to remove any features from my file system, then what
should I be removing and how should I be using tune2fs.  ( I am ready
and willing to experiment, but the thing I fear with tune2fs and
mke2fs is , it has chances of spoiling the whole thing :)


More information about the lfs-support mailing list