[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Resizing ext3 - incompatible feature enabled

From: Brian Cohen
Subject: Resizing ext3 - incompatible feature enabled
Date: Sat, 13 Nov 2004 11:38:44 -0700
User-agent: Mozilla Thunderbird 0.9 (X11/20041110)

I have seen this discussed in the past on this list but did not see any actual solutions. That said, I also have a new twist on it. Observe:

(parted) print
Disk geometry for /dev/hda: 0.000-76319.085 megabytes
Disk label type: msdos
Minor    Start       End     Type      Filesystem  Flags
1          0.031     31.007  primary   ext2        boot
2         31.008    519.750  primary   linux-swap
3        519.750  76319.085  primary   ext3
(parted) check 1
Error: Filesystem has incompatible feature enabled
(parted) check 2
Error: Partition /dev/hda2 is being used. You must unmount it before you modify
it with Parted.
(parted) check 3
Error: Filesystem has incompatible feature enabled

First, it says partitions 1 and 3 have and incompatible feature enabled. Second, it says partition 2 is in use, which it's not.

Now, past emails to this list have indicated that the dir_index feature was to blame, and that cleaering that flag would clear the error but introduce a new one about a 'strange layout'. However, the dir_index feature is not enabled on my ext3 filesystem (the one I eventually want to resize):

 Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          2b4e6b9b-ab47-4a6b-a9dc-780b859fb4d0
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features: has_journal ext_attr filetype sparse_super large_file
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              9715712
Block count:              19404630
Reserved block count:     970231
Free blocks:              18740665
Free inodes:              9544418
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:       Wed Nov 10 21:47:49 2004
Last mount time:          Sat Nov 13 16:58:28 2004
Last write time:          Sat Nov 13 16:59:13 2004
Mount count:              20
Maximum mount count:      26
Last checked:             Wed Nov 10 21:47:49 2004
Check interval:           15552000 (6 months)
Next check after:         Mon May  9 22:47:49 2005
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      7336472a-4511-4353-8a3d-4e077058b717

Does anyone have any ideas?

Thanks in advance,

-Brian Cohen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]