In Linux operating system, fsck (file system check) is a command-line utility that allows you to check file system and hard drive integrity. Using this tool, you can even fix some minor errors of file system. Generally, it runs automatically during system boot when Linux detects that the file system is not in consistent state, indicating improper system shutdown like power loss or system crash. However, if you run fsck tool on physical volume, you may come across some odd error messages. The errors prevent you from accessing your data and lead to data loss.

In the Linux operating system, the disks are mounted through labels, instead of device path. This is the most effective approach as the device name and path may change when you boot and thus may create several complications for the system and hence for the user.

So the disks are assigned labels so that the devices may mount up in the correct place. Thus disk labels are the important structure for the access of the Linux volumes. All entries for disks to be mounted at startup are in the file /etc/fstab.

Seeing that the development of the ext3 file system successor has started, and that Andrew Morton has released mm patch containing ext4 file system, I decided to run some simple benchmarks, even in this early stage of development.

Because the mm patch also contains Hans Reiser's reiser4 file system, I decided to run benchmarks against it, too, for a good measure. Let me once again remind that both ext4 and reiser4 are still in development, while ext3 has been in production for many years, so take all the results below with a grain of salt.

ZFS is an advanced modern filesystem from Sun Microsystems, originally designed for Solaris/OpenSolaris.

ZFS has many features which can benefit all kinds of users - from the simple end-user to the biggest enterprise systems:

• Provable integrity - it checksums all data (and metadata), which makes it possible to detect hardware errors (hard disk corruption, flaky IDE cables, etc...)
• Atomic updates - means that the on-disk state is consistent at all times, there's no need to perform a lengthy filesystem check after forced reboots or power failures
• Instantaneous snapshots and clones - it makes it possible to have hourly, daily and weekly backups efficiently, as well as experiment with new system configurations without any risks
• Built-in (optional) compression
• Highly scalable
• Pooled storage model - creating filesystems is as easy as creating a new directory. You can efficiently have thousands of filesystems, each with it's own quotas and reservations, and different properties (compression algorithm, checksum algorithm, etc...)
• Built-in stripes (RAID-0), mirrors (RAID-1) and RAID-Z (it's like software RAID-5, but more efficient due to ZFS's copy-on-write transactional model).
• Many others (variable sector sizes, adaptive endianness, ...)

sshfs is a very slick way to access your remote filesystems, securely and transparently. It is based on the great FUSE (Filesystem in Userspace) framework, which has been integrated in the linux kernel since version 2.6.14. While sshfs may not be as fast and featureful as other full-blown network filesystems such as NFS or Samba, it still has some great features: