similar to: Faster mkfs.ext3

Wow, it takes a really long time to make a 2TB ext2fs. Are there better-than-default options that could be used for a large filesystem? mke2fs 1.34 (25-Jul-2003) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 244203520 inodes, 488382016 blocks 24419100 blocks (5.00%) reserved for the super user First data block=0 14905 block groups 32768 blocks per group,

Hi, I want to use an ext3 Partition (~1TB) for Mail Storage, this means tons of small files. Has anyone recommendations about blocksize, inodes, etc. for mkfs.ext3 ? Thanks in advance, David -- View this message in context: http://www.nabble.com/Ext3----which-blocksize-for-small-files--tf2601442.html#a7257363 Sent from the Ext3 - User mailing list archive at Nabble.com.

I am reporting this on the advice of the Fedora Users Mailing List Member. This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. I am reporting this per suggestions made to me on the Fedora Users Mailing List. The following is the mailing list exchange: On 09/18/2014 07:01 PM, Robert Nichols wrote: > On

On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008 at gmail.com> wrote: > I am reporting this on the advice of the Fedora Users Mailing List Member. > > This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. > > I am reporting this per suggestions made to me on the Fedora Users Mailing List. I would

On Fri, Sep 19, 2014 at 07:56:37PM -0600, jd1008 wrote: > I am reporting this on the advice of the Fedora Users Mailing List Member. > > This the mailing list exchange outlining the problem with specifying -S to > mkfs, > and it's subsequent consequences when fsck is run. If none of the possible superblocks are valid when using mke2fs -b <NNN>, there's a good chance

Hi, I connected my harddisk which had ext3 filesystem and some files archived in it as slave device and issued "mkfs /dev/hdb2" accidentally. Immediately I issued Ctrl C and stopped the process. But before that it had deleted some 100 Blocks. After that I am unable to boot that hard disk as primary device. The system is asking me "please insert a valid boot device and press

Hi, I have an ext3 file system created with -T largefile4 option. Now it is running out of inode but it's only about 10% full. - Is there a way now to increase the number of inode without making a new file system? - If not, I am thinking about shrinking the file system, and then use the free up space to create a new file system with more inodes, and move the data over. Since I am

Hi, Why does mkfs.ocfs2 take so long compared to gfs2 (pretty fast iirc), xfs (almost instantaneous), or ext3 (slow but still ok)? I'm using: # mkfs.ocfs2 -F -b 4k -C 4k -L san1 -T mail /dev/vg/san1 mkfs.ocfs2 1.3.9 Overwriting existing ocfs2 partition. WARNING: Cluster check disabled. Proceed (y/N): y Filesystem Type of mail Filesystem label=san1 Block size=4096 (bits=12) Cluster size=4096

Hi, I made an ext3 filesystem with 8kB block size: # mkfs.ext3 -T largefile -v -b 8192 /dev/md0 Warning: blocksize 8192 not usable on most systems. mke2fs 1.38 (30-Jun-2005) Filesystem label= OS type: Linux Block size=8192 (log=3) Fragment size=8192 (log=3) 148480 inodes, 18940704 blocks 947035 blocks (5.00%) reserved for the super user First data block=0 290 block groups 65528 blocks per group,

i posted on rhel list about proper creating of 6tb ext3 filesystem and tuning here.......http://www.redhat.com/archives/nahant-list/2006-November/msg00239.html i am reading lots of ext3 links like...... http://www.redhat.com/support/wpapers/redhat/ext3/ http://lists.centos.org/pipermail/centos/2005-September/052533.html http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html ............but

I've got a 3.3TB ext3 on a FC3 64-bit system, running kernel 2.6.10-1.766FC3smp. I create the partition with parted 1.6.21, and I make the fs via: mkfs.ext3 -m1 -b 4096 -T largefile4 /dev/sda1 Works fine. bonnie++ running on it multiple times for days on end, no problems. However, I do the exact same setup on a RHEL4-AS i686 system, 32-bit, and the fs is totally hosed, get all kinds of

All, I'm requesting comments from the expert readers of ext3-users on these notes for tuning ext3 for performance. Most helpful would be feedback pertinent to RHEL 5; as XFS isn't supported under Red Hat Enterprise Linux these items are an attempt to match XFS performance with ext3. These items were culled from a number of sources. Will they be effective for achieving the performance

Here are 3 patches to avoid undesired aborts of mkfs.btrfs. These are based on top of Chris''s btrfs-progs.git: git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git Thanks, H.Seto Hidetoshi Seto (3): btrfs-progs: error if device for mkfs is too small btrfs-progs: error if device have no space to make primary chunks btrfs-progs: calculate available

On 09/20/2014 12:07 AM, Andreas Dilger wrote: > On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008@gmail.com> wrote: >> I am reporting this on the advice of the Fedora Users Mailing List Member. >> >> This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. >> >> I am reporting this per

Dear Srs, I get this error when running "mkfs.ocfs2": ================================================================================= # mkfs.ocfs2 -b 4K -C 32K -N 255 -L backup_ocfs2_001 /dev/sdb1 mkfs.ocfs2 1.2.7 Filesystem label=backup_ocfs2_001 Block size=4096 (bits=12) Cluster size=32768 (bits=15) Volume size=6000488677376 (183120382 clusters) (1464963056 blocks) 5678 cluster

Hi, So I've been hacking together an nbdkit plugin (similar to the "file" plugin, but it splits the file up into chunks): https://github.com/pepaslabs/nbdkit-chunks-plugin I got it to the point of being a working prototype. Then I threw it onto a raspberry pi, which it turns out only has a 50/50 shot of fallocate() working correctly. I'm checking the return code of

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

HI, I have just upgraded my Linux 7.1 to 7.2 (so I can have ext3 available for use). My question is how do I format a partition for an ext3 file system? We can normally run the command 'mkfs' or 'mkfs.ext2' to format an ext2 file system, or 'mkfs.xfs' for an xfs file system. I was looking for some utilily like 'mkfs.ext3' or similar. Question: Does ext3 support

I recently installed RedHat 8.0 on my computer but i discovered that i also needed to install windows for several programs that I still needed. I have two HDs, the RedHat install is on an 80Gb drive and the windows install is on an 8gb hard drive (which is the slave). I attempted to install windows on the slave but that is a no go so I powered down the computer and unhooked the ide cables

Situation: two similar servers, both with CentOS 5.4 64-bit. Making an ext3 filesystem on one takes seconds, on the other minutes. Partition Size Server 1 Server 2 1 GB 0.7 sec 0.3 sec 4 GB 2.5 sec 1.2 sec 40 GB 15 sec 13 min WTF e2fsprogs RPM is e2fsprogs-1.39-23.el5 on both systems mkfs --version reports