Problem with mkfs
in [Slackware]
|
From: Johannes D.H. Beekhuizen on 3 Jul 2010 14:24 Hello Robert, Robert Komar wrote: >> mke2fs: inode_size (128) * inodes_count (0) too big for a RK I've formatted larger partitions than that with ext2 and never RK had a problem (I've got a 2TB one mounted right now). It was the first time ever I had a problem with mkfs. On the old disk the partition was something like 120G. (What happened to the old times? In my first PC I decided to have a very big HD of 40M.) RK inodes_count of 0 and "filesystem with 0 blocks" is suspicious. RK Are you sure that /dev/sdc1 is the correct device name and RK that the partition table is correct? I did not understand that message really. But I thought the oartitiontable was correct, as I assumed that cfdisk did its work correctly. I also has the same effect with exct3 and ext4 by the way. I only took ext2 because it jappens to be the default in SlavkWare 13.0. Today I decided to try it again the rude way: I deleted all partitions, reran cfdisk and mkfs, and now it worked. I'm still puzzled. RK Also, use "-m 1" ... RK then "-T largefile" would probably help. I used the -m 1 this time. I love little tricks like that. Thanks for your help. -- Regards, Hans.
From: Robert Komar on 3 Jul 2010 17:35
Johannes D.H. Beekhuizen <jbeekhui(a)duinheks.nl> wrote: > Robert Komar wrote: {snip} > RK inodes_count of 0 and "filesystem with 0 blocks" is suspicious. > RK Are you sure that /dev/sdc1 is the correct device name and > RK that the partition table is correct? > > I did not understand that message really. But I thought the > oartitiontable was correct, as I assumed that cfdisk did its work > correctly. > I also has the same effect with exct3 and ext4 by the way. I only took > ext2 because it jappens to be the default in SlavkWare 13.0. > Today I decided to try it again the rude way: I deleted all partitions, > reran cfdisk and mkfs, and now it worked. I'm still puzzled. [snip} I still use ext2 for external drives that I connect through usb2, because I'm worried that the extra journaling traffic will slow down disk bandwidth even more. If your disk is connected directly to the ATA/SATA bus, then you are probably better off using ext3/ext4. You can convert from ext2 to ext3 easily using "tune2fs -j". Just make sure to update /etc/fstab with the new filesystem type for mounting during the next boot-up. Thanks for responding with news of your results; it always helps to know whether advice works or fails. Cheers, Rob Komar |