0001 What: /sys/block/loopX/loop/autoclear
0002 Date: Aug, 2010
0003 KernelVersion: v2.6.37
0004 Contact: linux-block@vger.kernel.org
0005 Description:
0006 (RO) Shows if the device is in autoclear mode or not ( "1" or
0007 "0"). Autoclear (if set) indicates that the loopback device will
0008 self-distruct after last close.
0009
0010 What: /sys/block/loopX/loop/backing_file
0011 Date: Aug, 2010
0012 KernelVersion: v2.6.37
0013 Contact: linux-block@vger.kernel.org
0014 Description:
0015 (RO) The path of the backing file that the loop device maps its
0016 data blocks to.
0017
0018 What: /sys/block/loopX/loop/offset
0019 Date: Aug, 2010
0020 KernelVersion: v2.6.37
0021 Contact: linux-block@vger.kernel.org
0022 Description:
0023 (RO) Start offset (in bytes).
0024
0025 What: /sys/block/loopX/loop/sizelimit
0026 Date: Aug, 2010
0027 KernelVersion: v2.6.37
0028 Contact: linux-block@vger.kernel.org
0029 Description:
0030 (RO) The size (in bytes) that the block device maps, starting
0031 from the offset.
0032
0033 What: /sys/block/loopX/loop/partscan
0034 Date: Aug, 2011
0035 KernelVersion: v3.10
0036 Contact: linux-block@vger.kernel.org
0037 Description:
0038 (RO) Shows if automatic partition scanning is enabled for the
0039 device or not ("1" or "0"). This can be requested individually
0040 per loop device during its setup by setting LO_FLAGS_PARTSCAN in
0041 in the ioctl request. By default, no partition tables are
0042 scanned.
0043
0044 What: /sys/block/loopX/loop/dio
0045 Date: Aug, 2015
0046 KernelVersion: v4.10
0047 Contact: linux-block@vger.kernel.org
0048 Description:
0049 (RO) Shows if direct IO is being used to access backing file or
0050 not ("1 or "0").
