15 managing disks - file system difference

By OK -
Understanding different filesystems
At the time of writing this, there are over 60 different filesystems available for Linux.
The following is a brief overview of the common ones you may frequently encounter:

- Btrfs: B-tree filesystem is a copy-on-write filesystem developed by Oracle in 2007.
It is still in the developmental stage and considered experimental. The intention
of Btrfs is to allow the filesystem to scale as drives get larger and larger. Because
of its benefits, it is being considered as the filesystem to replace ext4.

- ext2: It was introduced in 1993. This filesystem does not have journaling and hence,
has fewer writes per cycle, making it a good choice for flash drives.

ext3: It is very similar to ext2 with the addition of journaling, which improves
reliability, especially after an unclean shutdown.

- ext4: Being released in 2008, it is considered the successor of ext3. It can handle
volumes up to 1 exbibyte and files up to 16 tebibytes. This filesystem uses extents
to replace the traditional block mapping scheme used by earlier versions of ext.
It has enhancements allowing for faster filesystem checks (fsck).

- FAT: This is the abbreviation of File Allocation Table and the format was originally
used by DOS, OS/2, and Windows. It is available in the kernel mainly to provide
support for external devices such as USB flash drives.

-  ReiserFS (or Reiser3): It is a general purpose filesystem with journaling, originally
designed and written by Hans Reiser. When it was created, it contained many
features that were not yet available at the time including journaling, online growth,
and a scheme to limit internal fragmentation.

- Reiser4: It is the successor of ReiserFS (due to the conviction of the designer
Hans Reiser for murder, future development is uncertain).

  • XFS - default in RHEL7, but also in other recent Linux distributions
  • Ext4
  • btrfs
  • vfat
  • GFS2
  • Gluster

 XFS
based on a mature file system and has a healthy open source community behind it.
based on a B-tree database

 btrfs
Future promise
copy-on-write(CoW) file system (before writing to a file, original file is being copied)
Makes journaling unnecessary
Makes undelete unnecessary(you can rollback to previous version of file)
Support subvolumes

 A subvolume looks like a normal directory, with some additional operations described below. Subvolumes can be renamed or moved, nesting subvolumes is not restricted but has some implications regarding snapshotting.
A subvolume in btrfs can be accessed in two ways:
like any other directory that is accessible to the user
like a separately mounted filesystem (options subvol or subvolid)

 RHEL 7 FCS - first customer shipment

 ext4

 Pro:
  • supported by all distro's, commercial and not, and based on ext3, so it's widely tested, stable and proven
  • all kinds for nice features (like extents, subsecond timestamps) which ext3 does not have.
Con:
  • based on 1993 Ext2 file system
  • Uses H-tree scaling
  • Not very scalable
  • rumor has it that it is slower than ext3, the fsync dataloss soap
XFS

 Pro:
  • support for massive filesystems (up to 8 exabytes (yes, 'exa') on 64-bit systems)
  • online defrag
  • supported on upcoming RHEL6 as the 'large filesystem' option
  • proven track record: xfs has been around for ages
Con:
  • wikipedia mentions slow metadata operations, but I wouldn't know about that
  • potential dataloss on power cut, UPS is recommended, not really suitable for home systems
JFS

 Pro:
  • said to be fast (I have little experience with JFS)
  • originated in AIX: proven technology
Con:
  • used and supported by virtually no-one, except IBM (correct me if I'm wrong; I have never seen or heard about JFS used in production, though it obviously must be, somewhere)
ReiserFS

 Pro:
  • fast with small files
  • very space efficient
  • stable and mature
Con:
  • not very active project anymore, next generation reiser 4 has succeeded it
  • no online defragmenter
Reiser 4

 Pro:
  • very fast with small files
  • atomic transactions
  • very space efficient
  • metadata namespaces
  • plugin architecture, (crypto, compression, dedup and meta data plugins possible)
Con:
  • Reiser4 has a very uncertain future and has not been merged yet
  • main supporting distro (SuSE) dropped it years ago
  • Hans Reiser's 'legal issues' are not really helping
vfat

 compatible with other OS
useful for removable media

 GFS2
For Active/Active HA cluster environments
Only required if multiple nodes need to write to the same file system simultaneously
Regular file systems can be used in Active/Passive HA clusters

 Gluster
distributed file system
storage is in "bricks" that are spread over different servers. Bricks use XFS as their back-end file system.
useful in cloud environments

Comments

Post a Comment

Popular posts from this blog

HAproxy logging

By OK -
ubuntu@ubuntu:/etc/haproxy$ cat /etc/rsyslog.d/haproxy.conf # Create an additional socket in haproxy's chroot in order to allow logging via # /dev/log to chroot'ed HAProxy processes $ModLoad imudp $UDPServerRun 514 local0.* -/var/log/haproxy-0.log local1.* -/var/log/haproxy-1.log ### keep logs in localhost ## $AddUnixListenSocket /var/lib/haproxy/dev/log ------------------- ubuntu@ubuntu:/etc/haproxy$ cat /etc/haproxy/haproxy.cfg global chroot /var/lib/haproxy user haproxy group haproxy log 127.0.0.1   local0         log 127.0.0.1   local1 notice daemon frontend www     bind 192.168.40.128:8282    # haproxy public IP     default_backend as-backend    # backend used backend as-backend    balance leastconn    mode http  server as1 192.168.40.128:8082 check    # application srv 1 defaults log ...
Read more

teamcity Automatic Agent Start under Linux

By OK -
Automatic Agent Start under Linux To run agent automatically on the machine boot under Linux, configure daemon process with the  agent.sh start  command to start it and  agent.sh stop  command to stop it. Refer to an example procedure below: 1. Navigate to the services start/stop services scripts directory: cd /etc/init.d/ 2. Open the build agent service script: sudo vim buildAgent 3. Paste the following into the file : #!/bin/sh ### BEGIN INIT INFO # Provides: TeamCity Build Agent # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start build agent daemon at boot time # Description: Enable service provided by daemon. ### END INIT INFO #Provide the correct user name: USER="agentuser" case "$1" in start) su - $USER -c "cd BuildAgent/bin ; ./agent.sh start" ;; stop) su - $USER -c "cd BuildAgent/bin ; ./agent....
Read more

NFS mount add in fstab _netdev instead of default | firewall-cmd --list-all

By OK -
Redhat recommends us to add  _netdev  option for NFS file system in /etc/fstab. So that they can be mounted after starting the networking service. Alternative ways to refer to partitions: Label : LABEL=label Network ID Samba : //server/share NFS : server:/share SSHFS : sshfs#user@server:/share Device : /dev/sdxy (not recommended) Example #1 //192.168.1.134/share_name /mnt/share_name cifs username=server_user,password=server_password,_netdev 0 0 ^ Path to your share ^ Mountpoint ^ Username ^ Password ^ See note A Note A: The  _netdev  options makes sure the mount is only attempted AFTER a network connection has been established. Example #2 10.10.10.1:/vol1/fs1 /data nfs defaults,_netdev 0 0 ============================ [root@localhost ~]# firewall-cmd --list-all public   target: default   icmp-block-inversion: no   interfaces:   sources:   services: dhcpv6-client high-availabi...
Read more