of course it complains, it was a typo from me, sorry. The real command
was "btrfs check --readonly ...", just to ensure that no writing takes
place.
Nik.
--
2019-04-02 15:29, Hugo Mills:
On Tue, Apr 02, 2019 at 09:24:03PM +0800, Qu Wenruo wrote:
On 2019/4/2 下午9:06, Nik. wrote:
[snip]
On the larger file system only "btrfs check --repair --readonly ..." was
attempted (without success; most command executions were documented, so
the results can be made available), no writing commands were issued.
--repair will cause write, unless it even failed to open the filesystem.
If btrfs check accepted both --repair and --readonly without
complaining, then that's a regression and a bug. --readonly should be
mutually exclusive with any option that might write to the FS, and if
it isn't any more, then it's been broken and needs fixing.
Hugo.
