Frequent re-installations of operating system due to crashes is always been a problem for many of the linux users, and my case is also the same.... Everytime i start with doing something like trying some new commands or editing some configuration files and finally ends up with an 'OS crash' and a fresh installation thereafter.

By now, everyone knows that if you want to make a file unrecoverable, you can't simply delete it - you have to use a tool like 'shred' or 'srm' to overwrite its contents. But a common question is whether this is effective on an ext3, ext4, or other journaled filesystems. This article discusses these filesystems, and whether secure deletion tools work on them.

One of the features of Btrfs not found in other Linux file-systems (like EXT4) is support for copy-on-write snapshots / sub-volumes.

If I could choose one word to speak about Linux it would be "choice". After choosing the distribution, you have to choose the file system to store your data. Today, we have mainly the choice between Etx2, Ext3, Ext4 and XFS. Let's see whether different file systems have an impact on performance when we use Firebird databases.

In the never-ending quest for more performance, we examine three different journaling device options for ext4 with an eye toward improving metadata performance. Who doesn't like speed?

This article is meant to serve as a guide for migrating a live system from ext3 to an ext4 filesystem, including migration of files to use extents, a major feature in ext4.

The ext4 filesystem has been around for a while as experimental code in GNU/Linux distributions. Recently one distribution decided to make it the default for an install.

A number of senior kernel developers, including Linus Torvalds, Ted Ts'o, Alan Cox and Ingo Molnar, have been squabbling over the sense or otherwise of journaling and delayed allocation in Ext3 and Ext4.