Most file systems are based on a block device, which is a level of abstraction for the hardware responsible for storing and retrieving specified blocks of data, though the block size in file systems may be a multiple of the physical block size. In classical file systems, a single block may only contain a part of a single file. This leads to space inefficiency due to internal fragmentation, since file lengths are often not multiples of block size, and thus the last block of files will remain partially empty. This will create slack space, which averages half a block per file. Some newer file systems attempt to solve this through techniques called block suballocation and tail merging.
Block storage is normally abstracted by a file system or database management system for use by applications and end users. The physical or logical volumes accessed via block I/O may be devices internal to a server, direct attached via SCSI or Fibre Channel, or distant devices accessed via a storage area network (SAN) using a protocol such as iSCSI, or AoE. Database management systems often use their own block I/O for improved performance and recoverability as compared to layering the DBMS on top of a file system.
WIPO ASSIGNS PATENT TO MICROSOFT FOR "HEALTH REPORTING FROM NON-VOLATILE BLOCK STORAGE DEVICE TO PROCESSING DEVICE" (AMERICAN INVENTORS)
Jan 21, 2011; GENEVA, Jan. 21 -- Publication No. WO/2011/008586 was published on Jan. 20. Title of the invention: "HEALTH REPORTING FROM...
The split-path architecture: built for enterprise class virtualization.(Block Storage Virtualization)(split-path architecture)
Sep 01, 2006; Today, most application downtime results from planned outages associated with common IT maintenance tasks. For storage...