similar to: change sector size in EXT3

Hi, I have a doubt if I use the mke2fs option the right way. I formatted two different disks, one with $ mke2fs -b 4096 -E stride=16 -m 1 -T news /dev/sdd and the other with $ mke2fs -b 4096 -E stride=16 -m 1 -T largefile4 /dev/sde sdd is supposed to get files between 8k and 16k. sde will handle files with a fixed size of 32Mb. Then I tried this : $ dd if=/dev/zero of=/mount-sdx/file bs=4k

I want to convert all my NTFS partitions to ext3 since I'm no longer running Windows, at least on my main machine at home. I'm planning to tar the NTFS partitions to an existing ext3, reformat the partition as ext3 and untar it back. What is the best way to accomplish step two of this - reformatting the partition? I've only done this so far during the installation phase, and that

>Yes, if you are creating larger files. By default e2fsck assumes the average >file size is 8kB and allocates a corresponding number of inodes there. If, >for example, you are storing lots of larger files there (digital photos, MP3s, >etc) that are in the MB range you can use "-t largefile" or "-t largefile4" >to specify an average file size of 1MB or 4MB

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 there, Is there a utility to create an EXT3 file system image from directories? Just like the mkfs.jffs2 which creates a JFFS2 file system image from directories? The "mke2fs -j" only creates the bare bone file system, what I want is to build an image with pre-built content. Thanks, Debbie

I know there is no straightforward way to recover deleted files on an ext3 file system, but is there any way to recover from an accidental mke2fs? -- --------------------------------------------------------------- Paul Raines email: raines@nmr.mgh.harvard.edu MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging 149 (2301) 13th Street tel:(617)-724-2369

I am new to ext3 + external journal. Is there any howto I can look at? this is what I understand 1. mke2fs -O journal_dev /dev/md5 2. mke2fs -J device=/dev/md5 /dev/md0 3. mount /dev/md0 / -t ext3 ( hmm.. what do I need to put on fstab?? ) /dev/md5 is a two drive RAID 1 partition /dev/md0 is a 4 drive RAID 5 partition. questions: 1. I am running RedHat 9.0. what extra software I need to

Centos 5.1 documentation states that the supported ext3 filesystem limit is 16TB, yet I have a 9.5TB partition that is claimed to be too large: mke2fs 1.39 (29-May-2006) mke2fs: Filesystem too large. No more than 2**31-1 blocks (8TB using a blocksize of 4k) are currently supported. Am I missing something? > uname -a Linux fileserver.sharcnet.ca 2.6.18-53.1.6.el5 #1 SMP Wed Jan

Hi everyone, I've been running Redhat 7.2 (new install) for about 2 weeks now without any problems, but today I was not so lucky. My system hung while I was trying to configure the kernel-source RPM using 'xconfig'. After rebooting the system, it seems that my whole ext3 file system is corrupted. I get the message: Mounting root filesystem EXT3-fs: ide0(3,3):couldn't mount

Is there a way to create an ext3 filesystem (such as mke2fs will create an ext2 filesystem)? Is there a way to convert a vfat or ext2 filesystem to ext3? Thanks! SJR

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

We are having problems remounting an ext3 filesystem using an external journal device. The filesystem in question was working fine until the server was rebooted. This is what we see on dmesg when trying to mount: EXT3: failed to claim external journal device. The external journal lives on a LVM2 logical volume and it seems to be accessible ( we can dumpe2fs and see filesystem information).

Hello, seems like the new default ext2/ext3 256 bytes inode size problem applies to extlinux. HPA, could you confirm it? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491076 http://e2fsprogs.sourceforge.net/e2fsprogs-release.html E2fsprogs 1.40.5 (January 27, 2008) "Mke2fs will now create new filesystems with 256 byte inodes and the ext_attr feature flag by default. This allows for

After a (hardware) crash yesterday, I was unable to boot up due to unrecoverable ide errors (according to the printk()s) when accessing the root filesystem's journal for recovery. Unable to recover, I tried deleting the has_journal option, but that was disallowed given that the needs_recovery flag was set. I saw no way to unset that flag. Unable to access the backups (they were on a fw

I am trying to get a 9550SX to support a 1.5TB raid partition. I am unsure whether this is a driver problem, or an ext3 problem (as am getting some other wierdness detecting LUNs), but... fdisk recognizes the disk OK. I make a single extended partition with a single 1.5TB logical partition inside it. I then run mke2fs -j /dev/sdb It gets to writing inode tables, and wants to write 11176 block

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.

Hi folks, Yesterday I added a new disk to my box (sdb), and tried to 'mke2fs -j /dev/sdb' without making a partition on it firstly. mke2fs uttered some warning message asking me to confirm, and went on happily. Everything works fine after that, but I'm just wondering whether there's any difference or not between making fs on the whole block device and on a partition of it? Any

On Fri, Aug 30, 2013 at 12:07:22PM -0600, Andreas Dilger wrote: > > > [root@myhost /]# mkfs.ext3 /dev/sda1 > > mke2fs 1.35 (28-Feb-2004) > > First thing I would suggest is to update to a newer version of e2fsprogs, since this one is 9+ years old and that is a lot of > water under the bridge. That's definitely good advice, but even with e2fsprogs 1.35, if e2fsck -f is

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

Hi Ted and all, I have a couple of questions near the end of this message, but first I have to describe my problem in some detail. The power failure on Thursday did something evil to my ext3 file system (box running RH9+patches, ext3, /dev/md0, raid5 driver, 400GB f/s using 3x200GB IDE drives and one hot-spare). The f/s got corrupt badly and the symptoms are very similar to what Eddy described