51 lines · plain
1What: /sys/block/loopX/loop/autoclear2Date: Aug, 20103KernelVersion: v2.6.374Contact: linux-block@vger.kernel.org5Description:6 (RO) Shows if the device is in autoclear mode or not ( "1" or7 "0"). Autoclear (if set) indicates that the loopback device will8 self-distruct after last close.9 10What: /sys/block/loopX/loop/backing_file11Date: Aug, 201012KernelVersion: v2.6.3713Contact: linux-block@vger.kernel.org14Description:15 (RO) The path of the backing file that the loop device maps its16 data blocks to.17 18What: /sys/block/loopX/loop/offset19Date: Aug, 201020KernelVersion: v2.6.3721Contact: linux-block@vger.kernel.org22Description:23 (RO) Start offset (in bytes).24 25What: /sys/block/loopX/loop/sizelimit26Date: Aug, 201027KernelVersion: v2.6.3728Contact: linux-block@vger.kernel.org29Description:30 (RO) The size (in bytes) that the block device maps, starting31 from the offset.32 33What: /sys/block/loopX/loop/partscan34Date: Aug, 201135KernelVersion: v3.1036Contact: linux-block@vger.kernel.org37Description:38 (RO) Shows if automatic partition scanning is enabled for the39 device or not ("1" or "0"). This can be requested individually40 per loop device during its setup by setting LO_FLAGS_PARTSCAN in41 in the ioctl request. By default, no partition tables are42 scanned.43 44What: /sys/block/loopX/loop/dio45Date: Aug, 201546KernelVersion: v4.1047Contact: linux-block@vger.kernel.org48Description:49 (RO) Shows if direct IO is being used to access backing file or50 not ("1 or "0").51