From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Linux (Rated C-class, High-importance)
WikiProject icon This article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
C-Class article C  This article has been rated as C-Class on the project's quality scale.
 High  This article has been rated as High-importance on the project's importance scale.
High traffic

On 24 December 2008, Ext4 was linked from Slashdot, a high-traffic website. (See visitor traffic)

ext4 "extra" timestamp storage[edit]

The article originally claimed the following:

[...]In addition, 2 bits of the expanded timestamp field are added to the most significant bits of the seconds field of the timestamps to defer the year 2038 problem for an additional 500 years.

Although the article cited no source, some research found plenty of articles making this claim. For example, in this IBM article ( we find:

The time range has also be extended with two additional bits to increase the lifetime by another 500 years.

But the math doesn't support this claim. An additional two bits would increase the time range by

(3 \times 2^{31}) / 3600 / 24 / 365 \mbox{ years} \approx 204 \mbox{ years}

So either the nature of the change is wrong in these articles (it could be more than two bits) or the math is wrong. I took a look at the Linux kernel sources and this is the relevant code (;a=blob;f=fs/ext4/ext4.h;h=b77babe667f3cc323e24f71547581d44f7b6b6f0;hb=HEAD#l483):

static inline void ext4_decode_extra_time(struct timespec *time, __le32 extra)
       if (sizeof(time->tv_sec) > 4)
               time->tv_sec |= (__u64)(le32_to_cpu(extra) & EXT4_EPOCH_MASK)
                               << 32;
       time->tv_nsec = (le32_to_cpu(extra) & EXT4_NSEC_MASK) >> 2;

EXT4_EPOCH_MASK is 11 in binary. The 'extra' field is four bytes, most of which are used for finer grained precision. As the sources say, the code does in fact simply add two additional bits of precision to the seconds field. This means the increase is by 204 years, not 500 years. However, every source you can find (other than the code itself) says 500 years, so there is no correct source to cite. I went ahead and made the change anyway, but I'm posting here to explain that. Colin (talk) 23:38, 30 July 2009 (UTC)

And I'm reverting it. WP:OR is pretty clear on this point. You say yourself you can't find any published sources to back up your claim. NipokNek (talk) 11:51, 10 August 2009 (UTC)
Why would you revert it? I've clearly showed that the original information is wrong. If there's no source for the correct information, and that prevents it from being added, the conservative position would be to remove the claim entirely—not to reinstate wrong information. I don't like that this page has a completely wrong claim, so to avoid "original research", I've simply made the claim in the article more vague ("500 years" -> "several hundred years"). If this is still unacceptable, the section should be removed entirely. Propagating erroneous information simply because it's also found on an IBM page is foolish. Colin (talk) 02:11, 17 September 2009 (UTC)
The guidelines on specialists adding their own knowledge point out that you should still cite your source, so if you have investigated you should write an article explaining in detail what you did, on your blog maybe, and then you or someone else can cite your article and put in the correct information. --Petercoulton (talk) 14:37, 17 September 2009 (UTC)
With all due respect, that's totally nuts. According to the above rule, I couldn't correct a Wikipedia page that claimes 2+2=5 without citing a source. Simple arithmetic is not "specialist knowledge" that needs to be sourced. If you really need a source, here's one: I just checked (3 \times 2^{31}) / 3600 / 24 / 365.25 \mbox{ years} \approx 204.15 \mbox{ years} on my Casio fx-115ES calculator. (The \approx is there because a 204 year period may have a different number of leap years, but it's always 204, never 203 0r 205. Drop the ".15" and you can drop the \approx.) I am going to change the number in the article to the correct figure now. (talk) 16:09, 10 October 2009 (UTC)
The ext2 time field holds 2^{32} values. two extra bits gives a range of 2^{34}\mbox{ seconds} \approx 544\mbox{ years}. It's unclear if the earliest date representable is intended to be in 1970 or 1901. In the current implementation bugs means dates outside the 1970-2038 range don't work right. The existing (unsourced) infobox says 14 December 1901 - 25 April 2514, this is off by 68 years at one of the ends. BCoates (talk) 05:56, 8 January 2012 (UTC)


I'm not sure this article is appropriate as yet, since I don't think that it's gone past the proposal stage. Not sure if it should be deleted though. FrozenPurpleCube 16:42, 1 July 2006 (UTC)

At some point in the future we should have a page about ext4. However it is too early right now. So I've changed it to a redirect. If we did put it up for deletion and it was deleted, someone would just come along and replace it. So, IMHO, a redirect is good enough for now. AlistairMcMillan 19:01, 1 July 2006 (UTC)
 : Sorry I didn't read the discussion before re-creating the article. But I'll let it stay there if you want to remove it any way.

Travis| 2:22, 1 August 2006 (PST)

Yeah, considering that the page you linked to is from 1997, I don't think it's a valid inclusion anyway. Maybe in terms of historical perspective, if there is actually an EXT4 added to the Linux Source Tree. Until then, the redirect is best. FrozenPurpleCube 04:31, 2 August 2006 (UTC)
--- Topic for #linuxfs is Link to file system bugzilla entries now on || Some cool bugs there, check 'em out || Linus merged ext4 —Preceding unsigned comment added by (talkcontribs) 12 October 2006


Is it sure ext4 works on BSD and Mac OS X? I seriously doubt that. Can anyone bring more clarity to this matter, so we can remove those OS's if needed? Ludootje 10:23, 11 October 2006 (UTC)

If ext3 works, then parts of ext4 may work. But when using stuff like extents, you first need to add support for that to the BSD/OSX kernels. Read the paragraph about backward/forward compatibility. -Jen 15:46, 19 October 2006 (UTC)
I use BSD, both OpenBSD and FreeBSD. BSD does not support ext4. Not even FreeBSD, which tends to be ahead of the curve. BSD supports ext3, but only because ext3 is essentially ext2 with journaling thrown on top -- BSD actually only supports ext2, but because of the nature of ext3, it is able to mount it and edit it - it just doesn't respect the journaling feature. As far as Mac OS X, I haven't used it in some time, but I would be very surprised if Mac OS X could mount extfs, given it doesn't support UFS2, even though it has a "BSD subsystem." A lot of things that work on BSD systems do not work on Mac OS X. For example, no pf firewall, no /dev/audio or /dev/dsp, etc. Bearshark (talk) 04:30, 14 February 2010 (UTC)


The HTrees discussed are not explained sufficiently - the explanation needs to be extended or a new Wiki article needs to be created for "HTrees". Doronyg (talk) 14:30, 14 January 2008 (UTC)

It should probably be a page in itself since ext3 also uses htrees

Narayannewton (talk) 18:26, 14 January 2008 (UTC)

I agree that a page in itself would be better as htree been available since ext2 as a patch.

Ekscrypto (talk) 21:17, 3 February 2009 (UTC)


Is the table data structure a Hash Table? If it is it should have link to it. (talk) 18:52, 28 February 2008 (UTC)


Issue with the online defragmentation section: The section below is just pure rubbish.

Online defragmentation Ext4 will also have an online defragmenter. Even with the various techniques used to avoid it, a long lived file system does tend to become fragmented over time. Ext4 has a tool which can defragment individual files or entire file systems."

Here is my note to explain why this section must be corrected. NOTE: Come on! That is a total lie! Ext4 does NOT have a tool to defragment individual tools or entire filesystems! it just doesnt! If it does, I challenge the author of this unsupported statement to back up this claim with some information. What is this tool called? Where can I get it? Is is a production ready tool, or is it a kludged hack written to do some quick benchmarks/testing for an academic paper that was written early in 2007 and which has had little or no follow-up or adoption by users since then? There are 3rd party tools such as Shake which can be used to defrag any filesystem, including ext4, but they do so very inefficiently. Moving data off a partition, then back also defragments, but we don't say a filesystem has a defragmenter just because the standard unix commands mv or tar can be used to move data off then back onto the partition. Keep this discussion of Ext4 honest, or this wikipedia entry is worthless. The statement "Ext4 will also have an online defragmenter" is also a statement of hope and faith, and at this time is pure fantasy. Ext3 never got an online or offline defragmenter. How can anyone be 100% sure that ext4 will get one? Be honest. Admit that ext4 has no online or offline defragmenter. Feel free to state that an online defragmenter MAY be available in the future. That is all we can say at the moment.

I suggest the misleading statement on defragmentation be changed to something like the following:

Vague Promises of future Online defragmentation Ext4 may in future provide an online defragmenter. Even with the various techniques used to avoid it, a long lived file system does tend to become fragmented over time. Ext4 currently has no tool which can defragment individual files or entire file systems.

PS - if anyone thinks this defragmentation issue can continue to be glossed over by statements like those currently in this wiki page, they are mistaken. Defragmentation has been an appalling performance killer on ext3 and other filesystems for many years, and allowing untrue statements and vague promises from developers to gloss over these problems cannot be allowed anymore! Don't let them get away with it. Until these guys produce a proper online defragmenter - we should let it be known that the lack of one is a problem! If the true situation is actually publicised, and made clearly visible in wiki pages such as these, perhaps these developers will realise they have to actually produce a defragmenter BEFORE they can brag about having done so.

THANK YOU, on behalf of all linux users everywhere who have been putting up with fragged filesystems for years, because those in the know have refused to admit what a performance killer it is - and they've been reluctant to do that because the developers have never provided a solution, and so, to admit the standard linux filesystems are crippled by fragmentation is too embarrassing for linux lovers and can't be allowed...

—Preceding unsigned comment added by (talk) 02:03, 27 March 2008 (UTC)

Please see here. An online defragmenter already exists, it just isn't merged yet. And that's not counting the ability to treat ext4 filesystems as ext2 (depending on options) and use ext2 defragmenters on it. --Yamla (talk) 14:34, 27 March 2008 (UTC)
Also, I'd like to see a reliable source that indicates lack of online defragmentation in ext3 is a performance killer. I've been using ext3 in production environments for years and have not seen this performance issue on any system. Still, I'm not a reliable source. A simple link will suffice, no need to engage in inappropriate discussion about it here. --Yamla (talk) 14:36, 27 March 2008 (UTC)
Just to follow up, if anyone is trying to use this discussion as a reliable source (not a good idea), this page (5.10.11) indicates that it is probably not a good idea to use the ext2 defrag program even on an ext2 filesystem. However, it also indicates that fragmentation is really not a problem on Linux file systems. Other references I've found indicate that this may be a problem if your file system is over 90% of 95% full. --Yamla (talk) 21:32, 30 March 2008 (UTC)
I can only give you german sources, but theses state very clearly, that fragmentation of ext3 is a huge problem - and its design makes fragmentation worse than on some other filesystems (read this article about the "why?"). And even worse: Using the very old ext2 defrag, which has not been updated by programmers for nearly ten years now, on modern ext3 or ext2 flavours, which use techniques such as htrees, which were not present, when the in fact deprecated ext2 defrag was written, may damage your data. I am sorry, that I can only provide german sources, because I'm german and I don't know any english computer magazin that ever wrote about such stuff, but if you can read german, you'll see that your believe in the "unnecessity" of defragmentation on Linux file systems is just an Urban Legend. (I found the english version of that article) -- (talk) 12:10, 14 March 2010 (UTC)

Once again, we're told an online defragmenter exists, but... oh wait... its not available! Once again someone mentions the the ext2 defrag tool that has been obsolete and DANGEROUS for years. Noone in their right mind would use ext2defrag on an ext2 filesystem, let-alone on ext3 or ext4. Once again someone says that fragmentation is not an issue, just because they havent noticed it. How do you know its not an issue? Just because your production linux servers perform adequately, does not mean they couldn't perform better. Take one of your production filesystems and run a proper benchmark on it. Then copy all data off it, delete everything on it, copy data back, redo benchmark, be amazed. Saying it is not an issue is head-in-the-sand nonsense. Also, probably, what is occurring is that you have smart SCSI controllers which are letting your drives do out of order reads on all the fragments, reading them in the fastest way that they'll come off disk, and reassembling them in controller. That will mitigate the problem somewhat. Try using non-scsi controllers, ie an IDE or simple SATA drive - and you will be horrified - you will easily lose 50% or more of your disk speed due to fragmentation, and it doesnt take long, and you DONT have to run your drives to 95% full for it to happen - though, of course it will accelerate the fragging process if you do. —Preceding unsigned comment added by (talk) 05:51, 1 April 2008 (UTC)

This is not a discussion forum. Please see WP:NOT. --Yamla (talk) 15:41, 1 April 2008 (UTC)

errrr... there are three little tabs at the top of this Ext4 wiki page. In case you havent noticed... this IS the "discussion" tab... —Preceding unsigned comment added by (talk) 23:48, 1 April 2008 (UTC)

What part of "This is the talk page FOR DISCUSSING IMPROVEMENTS TO THE EXT4 ARTICLE" are you having trouble understanding? Please reference your claims and use them to improve the Wikipedia defragmentation page. Do that (Learn the rules about sourcing and NPOV first!) and you could be a valuable contributor instead of being disruptive. On THIS talk page the only part of what you wrote that has any bearing is the question of whether e4defrag exists. (talk) 16:42, 10 October 2009 (UTC)

I am just flabbergasted at the complete denial that everyone lives in w.r.t defragmentation. Yamla, you seem like a nice guy, i'm not trying to give you a hard time - but you said above that your link to tldp "indicates that it is probably not a good idea to use the ext2 defrag program even on an ext2 filesystem." But no, that is NOT what the tldp page indicated. What it actually said was: "However, it is HIGHLY recommended that you NOT use it. It was designed for and older version of ext2, and has not been updated since 1998! I only mention it here for references purposes." That means it would be sheer, utter, suicide to use that defragger. Don't gloss over that by saying oh its probably not a good idea to use it. No. Its worse than that. The simple fact is it just CANT be used ever by any sane person. A refernce to linux symposium nearly a year ago in June 2007 does not give ext4 an online defragger.

Why can't people just write a half-decent defragger for a modern linux filesystem! It doesnt have to be ultra-super-dooper-efficient. Just 100% safe, effective, and, reasonably efficient. Thats all. It's not asking too much. I don't like to seem ungrateful to open source software developers, i reckon they're great etc, I just wish they would stop trying to get me to swallow this sweetly coated poison pill, year after year. You will have a defragger they say. rrrgh. Ok for God/Allah's sake just produce said defragger so i can say "thank you thank you" and be happy, instead of being a sourpuss. —Preceding unsigned comment added by (talk) 00:17, 2 April 2008 (UTC)

This is not a general discussion forum for ext4. I have now semi-protected this page so that anonymous user,, can read this, which explains this in more detail. --Yamla (talk) 00:21, 2 April 2008 (UTC)

If anyone cares to check, the source is available for a work in progress version of the defragger available at [ h] , it is compilable if you commend out the comments and rename it to a .c file —Preceding unsigned comment added by (talk) 16:56, 16 July 2008 (UTC)

EXT4 will have a mutiblock allocator which will reduce fragmentation since ext4 will know ahead of time the file size only if delayed allocation is on-- (talk) 04:06, 16 July 2008 (UTC)

Bad jokes and other deleted nonsense?[edit]

I love how the article says that "H trees are higher alphabetically than B* trees", then points a citation to the Wikipedia article on Alphabetical order!

Comedic gold!--Dwedit (talk) 12:01, 20 June 2008 (UTC)

Creation date timestamps?[edit]

Could someone add a citation on whether ext4 will support creation date timestamps for files? I haven't found any information on this feature anywhere on the Internet and only this article on Wikipedia suggests that ext4 will support creation date timestamps leading me to believe that this is just wishful thinking. I believe we should delete this section in order to not create wrong expectations on ext4. —Preceding unsigned comment added by (talk) 07:35, 10 August 2008 (UTC)

Two fields (i_crtime and i_crtime_extra) which make up the creation time are present in the Linux kernel source (fs/ext4/ext4.h as of version 2.6.27-rc3.) I thus removed the "Citation needed" tag without actually adding one. C code is probably of little help to the typical user in this context, but anybody feel free to add a link if you think otherwise. —Preceding unsigned comment added by (talk) 11:17, 25 August 2008 (UTC)

"This article contains information about computer software currently in development."[edit]

This tag is placed at the top of this article. However, a file system is not software, correct? But it is in development so is that why we must accept the misnomer?PGScooter (talk) 06:58, 19 August 2008 (UTC)

I think this is entirely appropriate. A file system implementation is software. The Linux kernel implementation of ext4 is under development. Typically the FS's name refers to the file system itself as well as its original implementation. For example, you don't see people differentiating between the NTFS file system and Windows's NTFS code. -- intgr [talk] 13:38, 19 August 2008 (UTC)
"A file system implementation is software." Interesting, I did not know that. Thanks for the info :)PGScooter (talk) 04:12, 20 August 2008 (UTC)

backward/forward compatible[edit]

The uses of backward and forward compatible seem backwards to me and everyone I've talked to. The uses would be correct in relation to the "filesystem driver", but a backward compatable filesystem is clearly one that can be mounted with the previous version's driver, not the other way around! - (talk) 04:08, 12 November 2008 (UTC)

I totally disagree with your assessment. The text in this article as you have changed it now looks wrong. Please look at the articles linked: forward compatibility/backward compatibility, they agree with me. If you read those articles and still believe that I am incorrect, then I'll go through the trouble to find a source. If nobody replies here, I'm going to reverse the article text. ~a (usertalkcontribs) 23:23, 8 January 2009 (UTC)

I disagree with the use of "forward compatible". forward compatible means it is designed can accept input from future versiones (as specified in provided link): that would be ext5 (or whoever comes to replace ext4 en future). Backwards compatible, acording to provided link, means "allows input generated by older devices"; i'd understand that ext4 is backwards compatible in that "it can accept input generated by an ext3-aware OS", in other words, it's backward compatible since it can be mounted and treated as an ext3 file system. HuGo_87 (talk) 17:07, 30 January 2009 (UTC)

Linux 2.6.29 removes "noextents" mount option-- (talk) 12:49, 6 June 2009 (UTC)

I find the current version weird, too. To me, an ext4 file system is backward compatible with ext3 when it can be handled as ext3. —Preceding unsigned comment added by Huggie (talkcontribs) 13:11, 10 June 2009 (UTC)

Perhaps, extent seems not to be used until tune2fs -O extent is done. However, tune2fs -O ^extent cann't. -- (talk) 07:03, 11 June 2009 (UTC)

the size ext4 is built to support[edit]

Why is the phrase "the size ext4 is built to support" used in this article without clarification? Does this mean larger file systems, near the limit of what ext4 can support and beyond the size ext3 can support? Or does it mean any file system from only a few files up to that limit? —Preceding unsigned comment added by (talk) 13:03, 20 March 2009 (UTC)

AFAIK, an ext3 disk of only a few terabytes can take something like an hour to check. And without some optimizations this would grow so that a check of a 100 TB disk would be unrealistic to do at all. Also, the amount of RAM needed during the check can be a critical factor. Actually, there has been work going on to speed up fsck on ext3 as well, like [1], but I don't know whether it has been accepted into the kernel. Rune Kock (talk) 15:41, 20 March 2009 (UTC)
There's no actual need to fsck an ext3 file system anyway, as it's a journaling file system. -- intgr [talk] 16:00, 21 March 2009 (UTC)
Sorry intgr - that's not accurate. By default, most linux distros will actually force an fsck on boot for ext3 filesystems every X number of mounts (typically reboots) or Y number of days, whichever comes first - and in the event of power failure, while you don't *need* to FSCK, there are times when it's helpful. Disk corruption and various other things can cause it. Speaking as someone who's had to perform more than a few FSCKs of EXT3 filesystems on the various systems I manage or own, I have to disagree. Overand (talk) 19:24, 24 February 2010 (UTC)

Delayed allocation and potential data loss[edit]

In case anyone is interested, the patches that Ted Ts'o has written to mitigate this problem are: commit 8750c6d5fcbd3342b3d908d157f81d345c5325a7 ext4: Automatically allocate delay allocated blocks on rename and commit 7d8f9f7d150dded7b68e61ca6403a1f166fb4edf ext4: Automatically allocate delay allocated blocks on close [if the file was previously truncated] Rune Kock (talk) 22:12, 8 April 2009 (UTC)

By the way, this section, when I found it today, portrayed the problem as an "exposing API bugs" in the headline, and further down claimed that it was "really an application bug", as applications weren't calling fsync after they'd written to files. While the author clearly seems to think that this is the case, this is not the place to promote such an opinion. The content is therefore removed. Rōnin (talk) 01:36, 10 April 2009 (UTC)
(The opinion that is) Rōnin (talk) 01:37, 10 April 2009 (UTC)
I think that it can be substantiated by misc. standards that the only way for an application to assure itself that its data has been written to disk, is to call fsync or similar. So strictly speaking, it is an application bug that it doesn't call fsync after every important write. But it is clearly not a good idea for the file system to be so vulnerable. I would call it a case of "broken as designed": it follows the standard to the letter, but still eats your data. Rune Kock (talk) 17:05, 13 April 2009 (UTC)
If it really can be backed up by widely accepted standards that fsync() (or similar) has to be called, then of course it's admissible, as you say. It should at least be backed up by citations from the relevant standards, though, since just the initial discussion on Slashdot and elsewhere showed this to be a highly controversial issue. Rōnin (talk) 21:56, 13 April 2009 (UTC)

According to this page...

...the disadvantage listed under "Delayed allocation and potential data loss" can only happen if you purposely turn off the default barrier setting.


"Barriers on by default:

This is an option that improves the integrity of the filesystem at the cost of some performance (you can disable it with 'mount -o barrier=0', recommended trying it if you're benchmarking).

From this ( ) LWN article:

'The filesystem code must, before writing the [journaling] commit record, be absolutely sure that all of the transaction's information has made it to the journal. Just doing the writes in the proper order is insufficient; contemporary drives maintain large internal caches and will reorder operations for better performance. So the filesystem must explicitly instruct the disk to get all of the journal data onto the media before writing the commit record; if the commit record gets written first, the journal may be corrupted. The kernel's block I/O subsystem makes this capability available through the use of barriers; in essence, a barrier forbids the writing of any blocks after the barrier until all blocks written before the barrier are committed to the media. By using barriers, filesystems can make sure that their on-disk structures remain consistent at all times.' "

Unless I am misunderstanding the above, the the disadvantage listed under "Delayed allocation and potential data loss" appears to not exist in the most recent EXT4 version. I would welcome correction from someone with more technical knowledge in this area. (talk) 15:24, 10 October 2009 (UTC)

Missing sentence in introductory paragraph?[edit]

I noticed a bit of incoherency. The article starts off thus: "The ext4 or fourth extended filesystem is a journaling file system developed as the successor to ext3... However, other Linux kernel developers opposed accepting extensions to ext3 for stability reasons..." Why the 'however'? Who were the 'original' (as opposed to 'other') developers, who favored ext4 as an extension? (talk) 19:00, 7 May 2009 (UTC) / doctorcolossus

Benchmark on PostgreSQL[edit]

Various Linux OS using ext4 and recent kernel are suffering from performance hit on PostSQL. The issue is closely related to I/O performance. Is that a matter (or feature) of ext4? If that is true, it is good idea to include that.--Kittyhawk2 (talk) 09:23, 15 January 2010 (UTC)

Replacing file contents[edit]

"detect the occurrence of these common cases"

These cases? Which cases would those be? Can you be specific? -- (talk) 03:42, 2 May 2010 (UTC)

It was sort-of explained in the preceding section. But I rewrote most of it now, hopefully it's clearer? -- intgr [talk] 17:06, 2 May 2010 (UTC)

Features- Large FS[edit]

"Work is in progress at pu branch of e2fsprogs."

Does this make sense? I can't work out what that means, but it is late... Chaos.squirrel (talk) 14:46, 14 June 2010 (UTC)

"pu" is the name of a branch in the e2fsprogs git repository. But I think I'm going to remove it because it's not really encyclopedia material. -- intgr [talk] 22:06, 14 June 2010 (UTC)


Doesn't mention whether it's been adopted in Linux distributions... AnonMoos (talk) 17:19, 13 September 2011 (UTC)

  • It's in the kernel, so "Linux 2.6.28, 2.6.19" is sufficient — Preceding unsigned comment added by (talk) 14:27, 9 May 2012 (UTC)

Number of subdirectories[edit]

Currently, the article says that the number of subdirectories under ext3 is 32,000 and 64,000 under ext4. Those two numbers look suspiciously like somebody rounded 32K and 64K down. If so, wouldn't it be more accurate to use the exact numbers, possibly both as K and written out?JDZeff (talk) 20:33, 11 November 2011 (UTC)

Codepage of filenames ?[edit]

The table on the right hand side of the article states that allowed characters in filenames are all bytes except NULL and '/'.

It would be helpful to clarify whether ext4 is aware of characters or just of Bytes in its filenames; and if it is aware of characters, what codepage is used to store the characters. According to the description it is apparently aware of the character '/' ... Gandalf44 (talk) 01:10, 14 August 2012 (UTC)

In all "native" Linux file systems, file names are just a bunch of bytes. It's up to the user space to interpret what they mean. Some foreign Unicode-aware file systems have a "codepage=" mount option to specify how to convert characters back to a single-byte representation. -- intgr [talk] 08:45, 14 August 2012 (UTC)

The article tells the maximum filelength in ext4 to be 255 characters which seems to me to be missleading or at least unprecise as (at least in linux) the system does not care about character encoding. Since a UTF8 formated filename with 5 charaters can have more then 5 bytes (i.e. 10) it is entirely possible to have a filename being at maximum 127 characters in size. I would suggest updating the maximum filename length to state 255 bytes. — Preceding unsigned comment added by (talk) 06:29, 13 August 2013 (UTC)

Limits of Ext4 & Red Hat[edit]

I think there is an error in the limits mentioned by Red Hat. According to Red Hat ( The solution for large filesystems is to use XFS. The XFS file system is specifically targeted at very large file systems (16 TB and above).

According to Red Hat ( The maximum size they support for ext4 is 16TB. The maximum they support for XFS is 100TB for RHEL5 or RHEL6 and 500TB for RHEL7.

Under Features|Large file system, the text claims that Red Hat supports ext4 for file systems up to 100TB. That is untrue. They support ext4 file systems up to 16TB and XFS file systems up to 100TB (or 500TB in RHEL7).

Technical reasons for the 16TB limit is confirmed with this citations (already cited). — Preceding unsigned comment added by (talk) 21:30, 3 December 2014 (UTC)