similar to: 16TB ext3 mainstream - when?

Hi - We have had a raid failure, we have some what recovered but we continue to see the following ext3 message... Apr 17 14:59:14 acnlin84 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0); Apr 17 14:59:14 acnlin84 kernel: Possible IO failure. Since we have experienced several instances of ext3 file system corruption when we lose

I have an ext3 filesystem mounted r/w on 1 host and r/o on multiple hosts. Dangerous but cost effective. I recently implemented some protection through a fc switch that restricts some hosts to r/o access to the data luns. So if someone types mount -o rw or something, all is not lost. The issue occurs when it's mounted r/w on 1 host and another host attempts to mount it r/o. The mount

Hi, There wasn't much information regarding fragment support of ext2/3 since 2003 [1], Andreas stating that there were problems with the xattr implementation. Has this changed in the meanwhile? My second question is regarding the bytes-per-inode ratio: What benefits would I gain from having fewer inodes? I reckon it's only diskspace (if so, how much?). best regards, Michael Renner [1]

Hello, I looked through the archives a bit and could not find anything relevant, if you know otherwise please point me in the right direction. I have a ~3T ext3 filesystem on linux software raid that had been behaving corectly for sometime. Not to long ago it gave the following error after trying to mount it: mount: wrong fs type, bad option, bad superblock on /dev/md0, or too many

Hi, I've a question about the max. ext3 FS size. The ext3 FAQ explains that the limit is 4TB. http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html | Ext3 can support files up to 1TB. With a 2.4 kernel the filesystem size is | limited by the maximal block device size, which is 2TB. In 2.6 the maximum | (32-bit CPU) limit is of block devices is 16TB, but ext3 supports only up | to 4TB.

I need to setup a 3.27TB ext3 filesystem using -i 1024 and -b 1024. When I try to format this partition I get the "Filesystem too large." error. Are there any plans to update these limits? are there any patches already available that I can try out? Or am I just SOL here? (vzbu2 ~)# fdisk -l /dev/etherd/e1.1 Disk /dev/etherd/e1.1: 3600.7 GB, 3600795892224 bytes 255 heads, 63

Hi - We have had 3 rather major occurances of ext3 filesystem corruption lately, i.e. so bad we couldn't event mount, and fsck didn't help. I am looking for pointers, that could help us investigate the root cause. In general... We are running RedHat WS 3 Update 6, 2.4.21-40.2.ELsmp or 2.4.21-37.ELsmp We have a small SAN system that looks like this

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

Hi folks, For unknown cause I encounter following mounting problem; # /mnt/hda8 mount: wrong fs type, bad option, bad superblock on /dev/hda8, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so # dmesg | tail via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000)

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

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

Before we start accessing a huge (> 16 TiB) OCFS2 volume, we need to confirm that its journal supports 64-bit offsets. So we need to check the journal's feature bits before recovering the journal. This is not possible with JBD2 at present, because the journal superblock (where the feature bits reside) is not loaded from disk until the journal is recovered. This patch loads the journal

Dear list, pardon my ignorance on ext2/3fs. Is the ext2fs' 4Tb file system and 2GB maximum file size limit still true in ext3fs? Thanks for your reply, Gotze __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com

For future filesystem compatibility, we are wondering if there are any Lustre MDT filesystems in existence that have 2B or more total inodes? This is fairly unlikely, because it would require an MDT filesystem that is > 8TB in size (which isn''t even supported yet) and/or has been formatted with specific options to increase the total number of inodes. This can be checked with

For future filesystem compatibility, we are wondering if there are any Lustre MDT filesystems in existence that have 2B or more total inodes? This is fairly unlikely, because it would require an MDT filesystem that is > 8TB in size (which isn''t even supported yet) and/or has been formatted with specific options to increase the total number of inodes. This can be checked with

I have a file system I am trying to resize via resize2fs but I get this error resize2fs 1.41.14 (22-Dec-2010) resize2fs: New size too large to be expressed in 32 bits im on debian squeeze 2.6.32-5-amd64 # pvs ? PV???????? VG????? Fmt? Attr PSize? PFree ? /dev/md1?? vgRAID6 lvm2 a-?? 18.17t 134.12g # lvs ? LV??? VG????? Attr?? LSize? Origin Snap%? Move Log Copy%? Convert ? data1 vgRAID6 -wi-ao

Let me preface this by saying "Yes, I know *nix filesystems don't need to worry about fragmentation". That said, is there a way to check the overall level of fragmentation of a live ext3 filesystem? I know about filefrag, but that's for specific files. And I think e2fsck tells you, but only if you take the filesystem offline for the scan. Is there anything that will give

Hello What is the largest file size that can be created on Linux ? is there any limitation ? Thanks

Someone recently posted the following statement midway down the page at http://forums.gentoo.org/viewtopic-t-305871-postdays-0-postorder-asc-highlight-ext3+ordered+data-start-25.html >You don't need to defragment ext2/ext3 because as you use the >filesystem file blocks and inodes are moved around and reallocated >to keep the data nearly contiguous. It's not perfect, but it

Hi All, Can anyone help me in resolving this problem. I use Redhat 9 Enterprise edition. I have a session in which I logged in as a root. When I issue the command "su" from any other user it is throwing error "su : Incorrect password", If I try to change the password from the root session, it is throwing error "passwd : module unknown". [root at TESTING