1What: /sys/block/loopX/loop/autoclear 2Date: Aug, 2010 3KernelVersion: v2.6.37 4Contact: linux-block@vger.kernel.org 5Description: 6 (RO) Shows if the device is in autoclear mode or not ( "1" or 7 "0"). Autoclear (if set) indicates that the loopback device will 8 self-distruct after last close. 9 10What: /sys/block/loopX/loop/backing_file 11Date: Aug, 2010 12KernelVersion: v2.6.37 13Contact: linux-block@vger.kernel.org 14Description: 15 (RO) The path of the backing file that the loop device maps its 16 data blocks to. 17 18What: /sys/block/loopX/loop/offset 19Date: Aug, 2010 20KernelVersion: v2.6.37 21Contact: linux-block@vger.kernel.org 22Description: 23 (RO) Start offset (in bytes). 24 25What: /sys/block/loopX/loop/sizelimit 26Date: Aug, 2010 27KernelVersion: v2.6.37 28Contact: linux-block@vger.kernel.org 29Description: 30 (RO) The size (in bytes) that the block device maps, starting 31 from the offset. 32 33What: /sys/block/loopX/loop/partscan 34Date: Aug, 2011 35KernelVersion: v3.10 36Contact: linux-block@vger.kernel.org 37Description: 38 (RO) Shows if automatic partition scanning is enabled for the 39 device or not ("1" or "0"). This can be requested individually 40 per loop device during its setup by setting LO_FLAGS_PARTSCAN in 41 in the ioctl request. By default, no partition tables are 42 scanned. 43 44What: /sys/block/loopX/loop/dio 45Date: Aug, 2015 46KernelVersion: v4.10 47Contact: linux-block@vger.kernel.org 48Description: 49 (RO) Shows if direct IO is being used to access backing file or 50 not ("1 or "0"). 51