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

ext3 mkfs issues with a fresh file system ?



Hi all,

This is strange.
I created a file system on top of luks and does not have any data yet.
The very first fsck gives an error in the freshly created file system !

>>>>
$ sudo mke2fs -j /dev/mapper/cryptvol
mke2fs 1.41.2 (02-Oct-2008)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
19537920 inodes, 78142677 blocks
3907133 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
2385 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
   32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
   4096000, 7962624, 11239424, 20480000, 23887872, 71663616

Writing inode tables: done Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
$ sudo e2fsck -f -C0 /dev/mapper/cryptvol
e2fsck 1.41.2 (02-Oct-2008)
Superblock has an invalid ext3 journal (inode 8).
Clear<y>?
>>>>

--
Bhasker C V
Registered Linux user: #306349 (counter.li.org)
Fedora Ambassador    : Bhaslinux


Reply to: