Closed shumvgolove closed 4 years ago
Run mke2fs
manually without -q
option to see if it gives any clue.
I've got this:
$ mke2fs /dev/loop0 -F -b 4096 -U 3671e993-ecaa-44a9-baca-89935e15ffa9 -I 256 -r 1 -O has_journal,ext_attr,resize_inode,dir_index,^sparse_super2,filetype,extent,^journal_dev,flex_bg,^meta_bg,^mmp,64bit,^inline_data,^ea_inode,^large_dir,large_file,huge_file,sparse_super,^uninit_bg,dir_nlink,extra_isize,^bigalloc,metadata_csum,^project
mke2fs 1.45.6 (20-Mar-2020)
mke2fs: invalid blocks '-F' on device '/dev/loop0'
Try to move /dev/loop0
to the end. It appears mke2fs
get confused (not sure how) if the device is specified before -b
option.
Shouldn't /dev/loop0
be after the arguments? At least mke2fs man page suggest this.
Edit: sure, give me a moment.
Yes, as you have suggested, bringing /dev/loop0
as the last argument correctly creates the filesystem, but I am not sure tho why it passes device as the first argument.
musl's getopt()
implementation must diverge somehow.
Yes, we must follow each mkfs tool man page. I will prepare a PR.
Downstream issue.
In order to obtain files from the
.fsa
archive I use this simple trick:.fsa
:In the third step,
fsarchiver
throws this error:I am using Alpine Linux distribution, which in turn uses
musl
libc andbusybox
as user space toolset.