1 What: /sys/block/loopX/loop/autoclear 2 Date: Aug, 2010 3 KernelVersion: v2.6.37 4 Contact: linux-block@vger.kernel.org 5 Description: 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 10 What: /sys/block/loopX/loop/backing_file 11 Date: Aug, 2010 12 KernelVersion: v2.6.37 13 Contact: linux-block@vger.kernel.org 14 Description: 15 (RO) The path of the backing file that the loop device maps its 16 data blocks to. 17 18 What: /sys/block/loopX/loop/offset 19 Date: Aug, 2010 20 KernelVersion: v2.6.37 21 Contact: linux-block@vger.kernel.org 22 Description: 23 (RO) Start offset (in bytes). 24 25 What: /sys/block/loopX/loop/sizelimit 26 Date: Aug, 2010 27 KernelVersion: v2.6.37 28 Contact: linux-block@vger.kernel.org 29 Description: 30 (RO) The size (in bytes) that the block device maps, starting 31 from the offset. 32 33 What: /sys/block/loopX/loop/partscan 34 Date: Aug, 2011 35 KernelVersion: v3.10 36 Contact: linux-block@vger.kernel.org 37 Description: 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 44 What: /sys/block/loopX/loop/dio 45 Date: Aug, 2015 46 KernelVersion: v4.10 47 Contact: linux-block@vger.kernel.org 48 Description: 49 (RO) Shows if direct IO is being used to access backing file or 50 not ("1 or "0"). 51