[PATCH] livecd-iso-to-disk Create an ext4 filesystem by default for home.img

[Frederick Grose]

Author: Frederick Grose <fgrose(a)gmail.com&gt;
Date:   Tue Mar 8 16:37:16 2011 -0500

    Create an ext4 filesystem by default for home.img

diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh
index b7cee72..071943c 100755
--- a/tools/livecd-iso-to-disk.sh
+++ b/tools/livecd-iso-to-disk.sh
@@ -1134,14 +1134,14 @@ if [ "$homesizemb" -gt 0 -a -z "$skipcopy" ];
then
             cryptsetup luksOpen $loop EncHomeFoo
             setupworked=$?
         done
-        mke2fs -j /dev/mapper/EncHomeFoo
+        mke2fs -j -T ext4 /dev/mapper/EncHomeFoo
         tune2fs -c0 -i0 -ouser_xattr,acl /dev/mapper/EncHomeFoo
         sleep 2
         cryptsetup luksClose EncHomeFoo
         losetup -d $loop
     else
         echo "Formatting unencrypted /home"
-        mke2fs -F -j $TGTMNT/$LIVEOS/$HOMEFILE
+        mke2fs -F -j -T ext4 $TGTMNT/$LIVEOS/$HOMEFILE
         tune2fs -c0 -i0 -ouser_xattr,acl $TGTMNT/$LIVEOS/$HOMEFILE
     fi
 fi

[James Heather]

While we're on ext4 things, I wonder whether we could change the name of
the container file for the root filesystem? Currently it's called
'ext3.img', and contains an ext4 filesystem. It's not exactly a major
issue, but it does annoy me a little...

It would be better to call it 'fsroot.img' or something descriptive, to
avoid this kind of thing when ext94 comes out.

James

On Tue, 2011-03-08 at 21:43 +0000, Frederick Grose wrote:
>  Author: Frederick Grose <fgrose(a)gmail.com&gt;
>  Date:   Tue Mar 8 16:37:16 2011 -0500
>  
>  
>      Create an ext4 filesystem by default for home.img
>  
>  
>  diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh
>  index b7cee72..071943c 100755
>  --- a/tools/livecd-iso-to-disk.sh
>  +++ b/tools/livecd-iso-to-disk.sh
>  @@ -1134,14 +1134,14 @@ if [ "$homesizemb" -gt 0 -a -z "$skipcopy"
> ];
>  then
>               cryptsetup luksOpen $loop EncHomeFoo
>               setupworked=$?
>           done
>  -        mke2fs -j /dev/mapper/EncHomeFoo
>  +        mke2fs -j -T ext4 /dev/mapper/EncHomeFoo
>           tune2fs -c0 -i0 -ouser_xattr,acl /dev/mapper/EncHomeFoo
>           sleep 2
>           cryptsetup luksClose EncHomeFoo
>           losetup -d $loop
>       else
>           echo "Formatting unencrypted /home"
>  -        mke2fs -F -j $TGTMNT/$LIVEOS/$HOMEFILE
>  +        mke2fs -F -j -T ext4 $TGTMNT/$LIVEOS/$HOMEFILE
>           tune2fs -c0 -i0 -ouser_xattr,acl $TGTMNT/$LIVEOS/$HOMEFILE
>       fi
>   fi

[Brian C. Lane]

On Tue, Mar 08, 2011 at 10:43:05PM +0000, James Heather wrote:
>  While we're on ext4 things, I wonder whether we could change the
> name of
>  the container file for the root filesystem? Currently it's called
>  'ext3.img', and contains an ext4 filesystem. It's not exactly a major
>  issue, but it does annoy me a little...
>  
>  It would be better to call it 'fsroot.img' or something descriptive, to
>  avoid this kind of thing when ext94 comes out. 
Right now it is called ext3fs.img and any changes need to be coordinated
with dracut which actually handles mounting it.

-- 
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)

[Will Woods]

On Tue, 2011-03-08 at 15:23 -0800, Brian C. Lane wrote:
>  On Tue, Mar 08, 2011 at 10:43:05PM +0000, James Heather wrote:
>  > While we're on ext4 things, I wonder whether we could change the name of
>  > the container file for the root filesystem? Currently it's called
>  > 'ext3.img', and contains an ext4 filesystem. It's not exactly a major
>  > issue, but it does annoy me a little...
>  > 
>  > It would be better to call it 'fsroot.img' or something descriptive, to
>  > avoid this kind of thing when ext94 comes out.
>  
>  Right now it is called ext3fs.img and any changes need to be coordinated
>  with dracut which actually handles mounting it. 
I actually just sent a patch to upstream dracut to allow the use of
'btrfs.img':

http://article.gmane.org/gmane.linux.kernel.initramfs/1813

This could probably made even more general - it could accept *.img,
really. We'll see what upstream thinks..

-w

[Brian C. Lane]

On Wed, Mar 09, 2011 at 02:03:09AM -0500, Will Woods wrote:
>  On Tue, 2011-03-08 at 15:23 -0800, Brian C. Lane wrote:
>  > On Tue, Mar 08, 2011 at 10:43:05PM +0000, James Heather wrote:
>  > > While we're on ext4 things, I wonder whether we could change the name of
>  > > the container file for the root filesystem? Currently it's called
>  > > 'ext3.img', and contains an ext4 filesystem. It's not exactly a
> major
>  > > issue, but it does annoy me a little...
>  > > 
>  > > It would be better to call it 'fsroot.img' or something descriptive,
> to
>  > > avoid this kind of thing when ext94 comes out.
>  > 
>  > Right now it is called ext3fs.img and any changes need to be coordinated
>  > with dracut which actually handles mounting it.
>  
>  I actually just sent a patch to upstream dracut to allow the use of
>  'btrfs.img':
>  
>  http://article.gmane.org/gmane.linux.kernel.initramfs/1813
>  
>  This could probably made even more general - it could accept *.img,
>  really. We'll see what upstream thinks.. 
A generic name of some kind would be good, but probably not just *.img
as there may be some cases where other .img files are next to it. I like
fsroot.img myself.

-- 
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)

[Joseph D. Wagner]

Are you sure it's capital T and not lowercase t?

 From man:
        -t fs-type
               Specify the filesystem type (i.e., ext2, ext3, ext4, 
etc.) that is to be created.  If this  option  is  not
               specified,  mke2fs will pick a default either via how the 
command was run (for example, using a name of the
               form mkfs.ext2, mkfs.ext3, etc.) or via a default as 
defined by the /etc/mke2fs.conf(5) file.   This option
               controls  which  filesystem  options  are  used  by  
default,  based on the fstypes configuration stanza in
               /etc/mke2fs.conf(5).

               If the -O option is used to explicitly add or remove 
filesystem options that should be  set  in  the  newly
               created filesystem, the resulting filesystem may not be 
supported by the requested fs-type.  (e.g., "mke2fs
               -t ext3 -O extents /dev/sdXX" will create a filesystem 
that is not supported by the ext3 implementation  as
               found  in  the  Linux  kernel; and "mke2fs -t ext3 -O 
^has_journal /dev/hdXX" will create a filesystem that
               does not have a journal and hence will not be supported 
by the ext3 filesystem code in the Linux kernel.)

        -T usage-type[,...]
               Specify how the filesystem is going to be used, so that 
mke2fs can choose optimal filesystem parameters for
               that  use.   The  usage types that are supported are 
defined in the configuration file /etc/mke2fs.conf(5).
               The user may specify one or more usage types using a 
comma separated list.

               If this option is is not specified, mke2fs will pick a 
single default usage type based on the size  of  the
               filesystem to be created.  If the filesystem size is less 
than or equal to 3 megabytes, mke2fs will use the
               filesystem type floppy.  If the filesystem size is 
greater than 3 but less than or equal to 512  megabytes,
               mke2fs(8)  will  use  the  filesystem  small.   
Otherwise,  mke2fs(8)  will use the default filesystem type
               default.


On 03/08/2011 01:43 PM, Frederick Grose wrote:
>  Author: Frederick Grose <fgrose(a)gmail.com
> <mailto:[e-mail]>>
>  Date:   Tue Mar 8 16:37:16 2011 -0500
>
>      Create an ext4 filesystem by default for home.img
>
>  diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh
>  index b7cee72..071943c 100755
>  --- a/tools/livecd-iso-to-disk.sh
>  +++ b/tools/livecd-iso-to-disk.sh
>  @@ -1134,14 +1134,14 @@ if [ "$homesizemb" -gt 0 -a -z "$skipcopy" ];
> then
>               cryptsetup luksOpen $loop EncHomeFoo
>               setupworked=$?
>           done
>  -        mke2fs -j /dev/mapper/EncHomeFoo
>  +        mke2fs -j -T ext4 /dev/mapper/EncHomeFoo
>           tune2fs -c0 -i0 -ouser_xattr,acl /dev/mapper/EncHomeFoo
>           sleep 2
>           cryptsetup luksClose EncHomeFoo
>           losetup -d $loop
>       else
>           echo "Formatting unencrypted /home"
>  -        mke2fs -F -j $TGTMNT/$LIVEOS/$HOMEFILE
>  +        mke2fs -F -j -T ext4 $TGTMNT/$LIVEOS/$HOMEFILE
>           tune2fs -c0 -i0 -ouser_xattr,acl $TGTMNT/$LIVEOS/$HOMEFILE
>       fi
>   fi
>
>
>  --
>  livecd mailing list
>  livecd(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/livecd

[Frederick Grose]

On Tue, Mar 8, 2011 at 10:26 PM, Joseph D. Wagner <theman(a)josephdwagner.info
>  wrote: 
>  Are you sure it's capital T and not lowercase t?
>
>  From man:
>        -t fs-type
>               Specify the filesystem type (i.e., ext2, ext3, ext4, etc.)
>  that is to be created.  If this  option  is  not
>               specified,  mke2fs will pick a default either via how the
>  command was run (for example, using a name of the
>               form mkfs.ext2, mkfs.ext3, etc.) or via a default as defined
>  by the /etc/mke2fs.conf(5) file.   This option
>               controls  which  filesystem  options  are  used  by  default,
>   based on the fstypes configuration stanza in
>               /etc/mke2fs.conf(5).
>
>               If the -O option is used to explicitly add or remove
>  filesystem options that should be  set  in  the  newly
>               created filesystem, the resulting filesystem may not be
>  supported by the requested fs-type.  (e.g., "mke2fs
>               -t ext3 -O extents /dev/sdXX" will create a filesystem that is
>  not supported by the ext3 implementation  as
>               found  in  the  Linux  kernel; and "mke2fs -t ext3 -O
>  ^has_journal /dev/hdXX" will create a filesystem that
>               does not have a journal and hence will not be supported by the
>  ext3 filesystem code in the Linux kernel.)
>
>        -T usage-type[,...]
>               Specify how the filesystem is going to be used, so that mke2fs
>  can choose optimal filesystem parameters for
>               that  use.   The  usage types that are supported are defined
>  in the configuration file /etc/mke2fs.conf(5).
>               The user may specify one or more usage types using a comma
>  separated list.
>
>               If this option is is not specified, mke2fs will pick a single
>  default usage type based on the size  of  the
>               filesystem to be created.  If the filesystem size is less than
>  or equal to 3 megabytes, mke2fs will use the
>               filesystem type floppy.  If the filesystem size is greater
>  than 3 but less than or equal to 512  megabytes,
>               mke2fs(8)  will  use  the  filesystem  small.   Otherwise,
>   mke2fs(8)  will use the default filesystem type
>               default. 

Below are the reports from dumpe2fs 1.41.12 (17-May-2010)
on Fedora-14 (2.6.35.11-83.fc14.x86_64) of a 200 MiB image file.

The block sizes are 4096 bytes with -T and 1024 with -t.

Which would be preferred?

-T (mke2fs -F -j -T ext4 home.img):

Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          eb1e7223-73bf-46db-a84e-6c2a53120d65
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index
filetype needs_recovery extent flex_bg sparse_super large_file huge_file
uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              12800
Block count:              51200
Reserved block count:     2560
Free blocks:              46266
Free inodes:              12789
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      12
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         6400
Inode blocks per group:   400
Flex block group size:    16
Filesystem created:       Wed Mar  9 19:20:44 2011
Last mount time:          Wed Mar  9 19:23:05 2011
Last write time:          Wed Mar  9 19:23:05 2011
Mount count:              1
Maximum mount count:      -1
Last checked:             Wed Mar  9 19:20:44 2011
Check interval:           0 (<none>)
Lifetime writes:          19 MB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:          256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      27707648-c600-48df-b579-421863a91e4b
Journal backup:           inode blocks
Journal features:         (none)
Journal size:             16M
Journal length:           4096
Journal sequence:         0x00000001
Journal start:            0


Group 0: (Blocks 0-32767) [ITABLE_ZEROED]
  Checksum 0xce3c, unused inodes 6389
  Primary superblock at 0, Group descriptors at 1-1
  Reserved GDT blocks at 2-13
  Block bitmap at 14 (+14), Inode bitmap at 30 (+30)
  Inode table at 46-445 (+46)
  27848 free blocks, 6389 free inodes, 2 directories, 6389 unused inodes
  Free blocks: 4920-32767
  Free inodes: 12-6400
Group 1: (Blocks 32768-51199) [INODE_UNINIT, ITABLE_ZEROED]
  Checksum 0x9331, unused inodes 6400
  Backup superblock at 32768, Group descriptors at 32769-32769
  Reserved GDT blocks at 32770-32781
  Block bitmap at 15 ([phone]), Inode bitmap at 31 ([phone])
  Inode table at 446-845 ([phone])
  18418 free blocks, 6400 free inodes, 0 directories, 6400 unused inodes
  Free blocks: 32782-51199
  Free inodes: 6401-12800

-t (mke2fs -F -j -t ext4 home.img):

Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          1d70ce7d-b457-4fbd-9215-1963daa24b0d
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index
filetype needs_recovery extent flex_bg sparse_super huge_file uninit_bg
dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              51200
Block count:              204800
Reserved block count:     10240
Free blocks:              192691
Free inodes:              51189
First block:              1
Block size:               1024
Fragment size:            1024
Reserved GDT blocks:      256
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         2048
Inode blocks per group:   256
Flex block group size:    16
Filesystem created:       Wed Mar  9 19:34:33 2011
Last mount time:          Wed Mar  9 19:46:29 2011
Last write time:          Wed Mar  9 19:46:29 2011
Mount count:              1
Maximum mount count:      -1
Last checked:             Wed Mar  9 19:34:33 2011
Check interval:           0 (<none>)
Lifetime writes:          11 MB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:          128
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      454298cc-952e-46d6-8d74-8ea471649240
Journal backup:           inode blocks
Journal features:         (none)
Journal size:             4096k
Journal length:           4096
Journal sequence:         0x00000001
Journal start:            0


Group 0: (Blocks 1-8192) [ITABLE_ZEROED]
  Checksum 0x2df2, unused inodes 2037
  Primary superblock at 1, Group descriptors at 2-2
  Reserved GDT blocks at 3-258
  Block bitmap at 259 (+258), Inode bitmap at 275 (+274)
  Inode table at 291-546 (+290)
  3792 free blocks, 2037 free inodes, 2 directories, 2037 unused inodes
  Free blocks: 4401-8192
  Free inodes: 12-2048
Group 1: (Blocks 8193-16384) [INODE_UNINIT, ITABLE_ZEROED]
  Checksum 0xde7f, unused inodes 2048
  Backup superblock at 8193, Group descriptors at 8194-8194
  Reserved GDT blocks at 8195-8450
  Block bitmap at 260 ([phone]), Inode bitmap at 276 ([phone])
  Inode table at 547-802 ([phone])
  7934 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 8451-16384
  Free inodes: 2049-4096
Group 2: (Blocks 16385-24576) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0xa44e, unused inodes 2048
  Block bitmap at 261 ([phone]), Inode bitmap at 277 ([phone])
  Inode table at 803-1058 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 16385-24576
  Free inodes: 4097-6144
Group 3: (Blocks 24577-32768) [INODE_UNINIT, ITABLE_ZEROED]
  Checksum 0x3de9, unused inodes 2048
  Backup superblock at 24577, Group descriptors at 24578-24578
  Reserved GDT blocks at 24579-24834
  Block bitmap at 262 ([phone]), Inode bitmap at 278 ([phone])
  Inode table at 1059-1314 ([phone])
  7934 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 24835-32768
  Free inodes: 6145-8192
Group 4: (Blocks 32769-40960) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0x33d9, unused inodes 2048
  Block bitmap at 263 ([phone]), Inode bitmap at 279 ([phone])
  Inode table at 1315-1570 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 32769-40960
  Free inodes: 8193-10240
Group 5: (Blocks 40961-49152) [INODE_UNINIT, ITABLE_ZEROED]
  Checksum 0x6e1d, unused inodes 2048
  Backup superblock at 40961, Group descriptors at 40962-40962
  Reserved GDT blocks at 40963-41218
  Block bitmap at 264 ([phone]), Inode bitmap at 280 ([phone])
  Inode table at 1571-1826 ([phone])
  7934 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 41219-49152
  Free inodes: 10241-12288
Group 6: (Blocks 49153-57344) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0x142c, unused inodes 2048
  Block bitmap at 265 ([phone]), Inode bitmap at 281 ([phone])
  Inode table at 1827-2082 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 49153-57344
  Free inodes: 12289-14336
Group 7: (Blocks 57345-65536) [INODE_UNINIT, ITABLE_ZEROED]
  Checksum 0xc502, unused inodes 2048
  Backup superblock at 57345, Group descriptors at 57346-57346
  Reserved GDT blocks at 57347-57602
  Block bitmap at 266 ([phone]), Inode bitmap at 282 ([phone])
  Inode table at 2083-2338 ([phone])
  7934 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 57603-65536
  Free inodes: 14337-16384
Group 8: (Blocks 65537-73728) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0x2330, unused inodes 2048
  Block bitmap at 267 ([phone]), Inode bitmap at 283 ([phone])
  Inode table at 2339-2594 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 65537-73728
  Free inodes: 16385-18432
Group 9: (Blocks 73729-81920) [INODE_UNINIT, ITABLE_ZEROED]
  Checksum 0x0130, unused inodes 2048
  Backup superblock at 73729, Group descriptors at 73730-73730
  Reserved GDT blocks at 73731-73986
  Block bitmap at 268 ([phone]), Inode bitmap at 284 ([phone])
  Inode table at 2595-2850 ([phone])
  7934 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 73987-81920
  Free inodes: 18433-20480
Group 10: (Blocks 81921-90112) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0x7b01, unused inodes 2048
  Block bitmap at 269 ([phone]), Inode bitmap at 285 ([phone])
  Inode table at 2851-3106 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 81921-90112
  Free inodes: 20481-22528
Group 11: (Blocks 90113-98304) [INODE_UNINIT, ITABLE_ZEROED]
  Checksum 0x5993, unused inodes 2048
  Block bitmap at 270 ([phone]), Inode bitmap at 286 ([phone])
  Inode table at 3107-3362 ([phone])
  4096 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 94209-98304
  Free inodes: 22529-24576
Group 12: (Blocks 98305-106496) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0xec96, unused inodes 2048
  Block bitmap at 271 ([phone]), Inode bitmap at 287 ([phone])
  Inode table at 3363-3618 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 98305-106496
  Free inodes: 24577-26624
Group 13: (Blocks 106497-114688) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0x8229, unused inodes 2048
  Block bitmap at 272 ([phone]), Inode bitmap at 288 ([phone])
  Inode table at 3619-3874 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 106497-114688
  Free inodes: 26625-28672
Group 14: (Blocks 114689-122880) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0x8bc0, unused inodes 2048
  Block bitmap at 273 ([phone]), Inode bitmap at 289 ([phone])
  Inode table at 3875-4130 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 114689-122880
  Free inodes: 28673-30720
Group 15: (Blocks 122881-131072) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0xb824, unused inodes 2048
  Block bitmap at 274 ([phone]), Inode bitmap at 290 ([phone])
  Inode table at 4131-4386 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 122881-131072
  Free inodes: 30721-32768
Group 16: (Blocks 131073-139264) [INODE_UNINIT, ITABLE_ZEROED]
  Checksum 0x3f30, unused inodes 2048
  Block bitmap at 131073 (+0), Inode bitmap at 131089 (+16)
  Inode table at 131105-131360 (+32)
  5870 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 131082-131088, 131098-131104, 133409-139264
  Free inodes: 32769-34816
Group 17: (Blocks 139265-147456) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0xc772, unused inodes 2048
  Block bitmap at 131074 ([phone]), Inode bitmap at 131090 ([phone])
  Inode table at 131361-131616 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 139265-147456
  Free inodes: 34817-36864
Group 18: (Blocks 147457-155648) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0x2cb8, unused inodes 2048
  Block bitmap at 131075 ([phone]), Inode bitmap at 131091 ([phone])
  Inode table at 131617-131872 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 147457-155648
  Free inodes: 36865-38912
Group 19: (Blocks 155649-163840) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0x9f43, unused inodes 2048
  Block bitmap at 131076 ([phone]), Inode bitmap at 131092 ([phone])
  Inode table at 131873-132128 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 155649-163840
  Free inodes: 38913-40960
Group 20: (Blocks 163841-172032) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0x84cd, unused inodes 2048
  Block bitmap at 131077 ([phone]), Inode bitmap at 131093 ([phone])
  Inode table at 132129-132384 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 163841-172032
  Free inodes: 40961-43008
Group 21: (Blocks 172033-180224) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0x08d4, unused inodes 2048
  Block bitmap at 131078 ([phone]), Inode bitmap at 131094 ([phone])
  Inode table at 132385-132640 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 172033-180224
  Free inodes: 43009-45056
Group 22: (Blocks 180225-188416) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0xe31e, unused inodes 2048
  Block bitmap at 131079 ([phone]), Inode bitmap at 131095 ([phone])
  Inode table at 132641-132896 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 180225-188416
  Free inodes: 45057-47104
Group 23: (Blocks 188417-196608) [INODE_UNINIT, BLOCK_UNINIT, ITABLE_ZEROED]
  Checksum 0x2f21, unused inodes 2048
  Block bitmap at 131080 ([phone]), Inode bitmap at 131096 ([phone])
  Inode table at 132897-133152 ([phone])
  8192 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 188417-196608
  Free inodes: 47105-49152
Group 24: (Blocks 196609-204799) [INODE_UNINIT, ITABLE_ZEROED]
  Checksum 0x8bfc, unused inodes 2048
  Block bitmap at 131081 ([phone]), Inode bitmap at 131097 ([phone])
  Inode table at 133153-133408 ([phone])
  8191 free blocks, 2048 free inodes, 0 directories, 2048 unused inodes
  Free blocks: 196609-204799
  Free inodes: 49153-51200

[Brian C. Lane]

On Wed, Mar 09, 2011 at 11:21:45PM -0500, Frederick Grose wrote:
>  The block sizes are 4096 bytes with -T and 1024 with -t.
>  
>  Which would be preferred?
>   
Smaller blocks are probably better since we're normally going to be
dealing with smaller filesystems.

What I think I'll do is change it to mkfs.ext4 and let it use the
defaults like -T describes.

-- 
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)

[Frederick Grose]

On Thu, Mar 10, 2011 at 7:03 PM, Brian C. Lane <bcl(a)redhat.com&gt; wrote:

>  On Wed, Mar 09, 2011 at 11:21:45PM -0500, Frederick Grose wrote:
>  > The block sizes are 4096 bytes with -T and 1024 with -t.
>  >
>  > Which would be preferred?
>  >
>
>  Smaller blocks are probably better since we're normally going to be
>  dealing with smaller filesystems.
>
>  What I think I'll do is change it to mkfs.ext4 and let it use the
>  defaults like -T describes.
>  
Confirmed that
 mkfs.ext4 -F -j home.img

produces the same structure as
 mke2fs -F -j -t ext4 home.img

did in my tests described earlier.

     --Fred

>  --
>  Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA
>  (PST8PDT)
>