public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yano Ray <yanorei@hotmail.co.jp>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: fsync() cause "Invalid Argument" for block device.
Date: Sat, 21 Jan 2023 05:57:35 +0000	[thread overview]
Message-ID: <TYAPR01MB63808568168145322E9D9862B8CA9@TYAPR01MB6380.jpnprd01.prod.outlook.com> (raw)

Hi,
I tried to format a partition using mkfs.ext4 (e2fsprogs) but it failed with an error.

$ /usr/sbin/mkfs.ext4 /dev/sde1
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with 16384 1k blocks and 4096 inodes
Filesystem UUID: fb09cfbf-9f2a-4874-82f7-26c7cb853093
Superblock backups stored on blocks:
        8193

Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: mkfs.ext4: Invalid argument while writing out and closing file system
$ 

This also seems to happen with mkfs.minix (linux-utils).

$ /sbin/mkfs.minix /dev/sde1
5472 inodes
16384 blocks
Firstdatazone=176 (176)
Zonesize=1024
Maxsize=268966912

mkfs.minix: write failed: Invalid argument
$ 

I think it's because fsync is not implemented (causes InvalidArgument) for block devices.
Why fsync is not implemented for block devices?

/* test code */
#include <unistd.h>
#include <fcntl.h>
#include <errno.h>
#include <stdio.h>
#include <string.h>

int main(int argc, char** argv) {
  int fd;

  if (argc != 2) {
    puts("./program [file]");
    return -1;
  }

  fd = open(argv[1], O_RDWR);
  printf("open: %s\n", strerror(errno));
  if (errno) return -1;

  fsync(fd);
  printf("fsync: %s\n", strerror(errno));
  if (errno) return -1;
}

on Cygwin:
$ ./a.exe /dev/sde
open: No error
fsync: Invalid argument
$ ./a.exe /dev/sde1
open: No error
fsync: Invalid argument
$ uname -a
CYGWIN_NT-10.0-22621 DESKTOP-5H6F7L3 3.4.5-1.x86_64 2023-01-19 19:09 UTC x86_64 Cygwin
$ 

expected behaviour (on Arch Linux):
$ sudo ./a.out /dev/sda
$ sudo ./a.out /dev/sda
open: Success
fsync: Success
$ sudo ./a.out /dev/sda1
open: Success
fsync: Success
$ uname -a
Linux arch 6.0.11-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 02 Dec 2022 17:25:31 +0000 x86_64 GNU/Linux
$

Thanks,

---
Rei Yano <yanorei@hotmail.co.jp>

             reply	other threads:[~2023-01-21  5:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21  5:57 Yano Ray [this message]
2023-01-21 12:32 ` Takashi Yano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=TYAPR01MB63808568168145322E9D9862B8CA9@TYAPR01MB6380.jpnprd01.prod.outlook.com \
    --to=yanorei@hotmail.co.jp \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).