On 27 September 2013 22:13, James Harper <james.harper@bendigoit.com.au> wrote:
I've chosen a 4MB of data per inode ratio based on some rough calculations, but while my mkfs.ext3 <dev> -i 4194304 just raced through initially, when it got to "Writing superblocks and filesystem accounting information:" it just seemed to hang. Strace says it's doing seek, write 4k, seek, write 4k, over and over again. I hit ^C and the process is now [mkfs.ext3], but the system is still pegged at 100% disk utilisation.
( sorry James for the double reply ) Hi, I am no expert but in case it helps I have used mkfs.ext3 -T largefile4 in the past without problems on a single 1TB drive and it was a little faster, not slower, than other mkfs. According to /etc/mke2fs.conf that is equivalent to inode_ratio = 4194304 blocksize = -1 so if I was seeing your symptoms I wouldn't be blaming that. Maybe test it on an individual drive/s first?