50 lines · 1.4 KB · Text
RawDownload
What:		/sys/block/loopX/loop/autoclearDate:		Aug, 2010KernelVersion:	v2.6.37Contact:	linux-block@vger.kernel.orgDescription:		(RO) Shows if the device is in autoclear mode or not ( "1" or		"0"). Autoclear (if set) indicates that the loopback device will		self-distruct after last close. What:		/sys/block/loopX/loop/backing_fileDate:		Aug, 2010KernelVersion:	v2.6.37Contact:	linux-block@vger.kernel.orgDescription:		(RO) The path of the backing file that the loop device maps its		data blocks to. What:		/sys/block/loopX/loop/offsetDate:		Aug, 2010KernelVersion:	v2.6.37Contact:	linux-block@vger.kernel.orgDescription:		(RO) Start offset (in bytes). What:		/sys/block/loopX/loop/sizelimitDate:		Aug, 2010KernelVersion:	v2.6.37Contact:	linux-block@vger.kernel.orgDescription:		(RO) The size (in bytes) that the block device maps, starting		from the offset. What:		/sys/block/loopX/loop/partscanDate:		Aug, 2011KernelVersion:	v3.10Contact:	linux-block@vger.kernel.orgDescription:		(RO) Shows if automatic partition scanning is enabled for the		device or not ("1" or "0"). This can be requested individually		per loop device during its setup by setting LO_FLAGS_PARTSCAN in		in the ioctl request. By default, no partition tables are		scanned. What:		/sys/block/loopX/loop/dioDate:		Aug, 2015KernelVersion:	v4.10Contact:	linux-block@vger.kernel.orgDescription:		(RO) Shows if direct IO is being used to access backing file or		not ("1 or "0").