On 26/01/15 10:32, Karel Zak wrote: > On Mon, Jan 26, 2015 at 02:24:04AM +0100, Michael Biebl wrote: >>> -l Create an exclusive flock(2) lock file >>> (/run/fsck/<diskname>.lock) for whole-disk >>> device. This option can be used with one device only (this >>> means that -A and -l are >>> mutually exclusive). This option is recommended when more >>> fsck(8) instances are exe- >>> cuted in the same time. The option is ignored when used for >>> multiple devices or for >>> non-rotating disks. fsck does not lock underlying >>> devices when executed to check >>> stacked devices (e.g. MD or DM) - this feature is not >>> implemented yet. >> >> Karel, is there an upstream bug report for this issue? What's the state >> of this feature, is it actively being worked on? > No, nobody is workning on -l for stacked devices. > > Karel >
Is there any other workaround, or should people consider moving to BtrFs instead of using LVM on md? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
